Rob Soukoreff: "gcc questions" (Jan 16, 16:35):Ok, this comes up every once in a while, and I agree a FAQ would be a good idea. We had one, but it got out-of-date even before it was ready: linux has evolved rather quickly. Just as a pointer, there are linux-activists mail collected at tsx-11 (or was some time ago), and people new on the list might want to know what the problems of yesterweek have been. Gcc can install in several directories, but the following is what I use: from gccbin.tar: /usr/local/bin - gcc /usr/local/lib - all the other stuff /usr/local/bin needs to be in the path (as an aside: bash-1.11 has a bug which results in an abort() if your path ends in a colon, and you try to execute something that doesn't exists: eg xyzzy). include.tar.Z should untar to the /usr/include -directory tree if you untar it in the root directory. Check with "tar tf include.tar". lib.tar.Z doesn't need to go in any special place: I have a source tree under /usr/src, and I put it under that. You don't need this file unless you want to recompile the library. Additionally, I've linked (use symbolic links if you wish, testing out new features) gcc to just 'cc', as that means I sometimes don't have to change the makefiles at all. Likewise, gcc-ld, gcc-as, gcc-ar can with success be linked to the files 'gld', 'gas' and 'gar', somewhere on the path. I have all the /usr/local/lib/gcc-XX files linked both to /usr/local/bin/XX and /usr/local/bin/gXX. Linus
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| James Bottomley | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| David Miller | [GIT]: Networking |
| Antonio Almeida | HTB accuracy for high speed |
| Ingo Molnar | iwlwifi: fix build bug in "iwlwifi: fix LED stall" |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Avi Kivity | Re: [RFC PATCH 14/17] kvm: add a reset capability |
git: | |
