----------
> > gcc -V 2.7.2 should cause the newer gcc/egcs compilers to "act" like
gcc
> > 2.7.2
>
> Only if you have that version of gcc still installed on your PC. You'll
> likely need the appropriate -b or even -B command line option, though.
>
> centurion:~ > ls /usr/lib/gcc-lib/
> i386-redhat-linux i686-pc-linux-gnu
>
> centurion:~ > ls /usr/lib/gcc-lib/i386-redhat-linux/
> 2.7.2.3 egcs-2.90.27 egcs-2.90.29
>
> centurion:~ > ls /usr/lib/gcc-lib/i686-pc-linux-gnu/
> pgcc-2.91.57 pgcc-2.91.60
>
> my 'gcc' binary defaults to 2.7.2.3, but if i want to invoke, say,
> pgcc-2.91.60, i'd have to use 'gcc -Vpgcc-2.91.60 -bi686-pc-linux-gnu'.
>
true, though most people may just put it in /usr/local.
> > ./configure <host> <target> <build>
>
> Configure checks enviroment though. You can do any of these:
>
> (bash/sh, possibly other sh-alikes)
>
> > CC="gcc -V2.7.2.3 -bi386-redhat-linux" ./configure [your options]
>
> or
>
> > export CC="/gnusr/local/bin/gcc -V2.8.1 -B/gnusr/local/libble \
> -bi486-rms-lignux -O42 -fno-inline" [*]
> > ./configure [your options]
>
> (csh/tcsh-alikes)
>
> > env CC="gcc -V2.7.2.3 -bi386-redhat-linux" ./configure [your options]
>
> or
>
> > setenv CC "/gnusr/local/bin/gcc -V2.8.1 -B/gnusr/local/libble \
> -bi486-rms-lignux -O42 -fno-inline" [*]
> >./configure [your options]
>
> You can also set the 'CFLAGS' env variable for the options, i can imagine
> that is considered slightly 'cleaner'.
>
most people go with the "factory defaults", though.
> Regards,
> Thomas.
>
> [*]: Yes, your system would have to be really sick to have such a
setup...
> but it would be amusing trying to find out which utilities are able to
> cope with it and which aren't. :)
some people compile with libc5 and libc6.
Matthew D. Pitts
mpitts@suite224.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/