Joined: Sep. 2005
||Posted: Dec. 17 2007,08:22
Thanks very nuch for compile.uci - just used it to sucessfully build gnupg2 (being posted)!
| have not seen any adverse effects compiling modules (eg bluetooth, irda, cifs) with the compile extension,|
Andrewb is right - modules have to be compiled with the same gcc (and I think binutils) version as was the kernel. If not, they might appear to work ok, but unpredictable things could happen, which in the kernel could be very bad. If modules have been posted that were not compiled with gcc-2.95, these should be pulled immediately and rebuilt.
|maybe it would be better to add a symlink gcc -> gcc-2.95|
I suggest not doing that. As we know, gcc-2.95 needs to be co-installed with eg gcc-with-libs on dsl when compiling the kernel or modules and these versions need to be kept seperate for other compiles. It's better to explicitly point at CC=gcc-2.95 in the environment or if necessary in the Makefile if it doesn't say that already when building a module (the 2.4.xx kernel config points at it anyway and at least some module sources will get the gcc version from the kernel sources). Then we're aware that we are doing so and these versions don't get mixed up. gcc-2.95 is not recommended for compiling anything but the 2.4.xx kernel and modules since it's incapable of doing i686 optimization properly and is generally a pretty crappy gcc version.