On Wed, 1 Nov 2000, Jeff Garzik wrote:
> Alan Cox wrote:
> > Mandrake kgcc I believe is egcs 1.1.2
>
> Correct...
>
> Though Richard Henderson's message recent about 'gcc -V ...' not doing
> the right thing has me worried... egcs 1.1.2 not gcc 2.95.2 is
> definitely being called when '/usr/bin/kgcc' is executed, but I'm still
> worried that some details might be getting lost...
> http://boudicca.tux.org/hypermail/linux-kernel/2000week44/1069.html
It's best to use a seperate driver for each compiler. I don't know of
any other way it can bite you, but one way is if you if you have drivers
built with different arch names trying to call the right compiler innards
with -V. You also need -b archname for it to get it right.
[root]:# gcc -v
Reading specs from /usr/lib/gcc-lib/i586-linux-gnu/gcc-2.95.2/specs
gcc version gcc-2.95.2 19991024 (release)
[root]:# gcc -V 2.8.1 -v
Using builtin specs. <== danger Will Robinson. (think about includes etc)
gcc driver version gcc-2.95.2 19991024 (release) executing gcc version 2.8.1
[root]:# gcc -V 2.8.1 -b i486-linux-gnu -v
Reading specs from /usr/lib/gcc-lib/i486-linux-gnu/2.8.1/specs
gcc driver version gcc-2.95.2 19991024 (release) executing gcc version 2.8.1
I always diddle Makefile.in to build/install the driver with a non gcc
name for this reason. Each driver knows where it's innards lives without
needing to be told (and risking me accidentally telling it lies:)
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
