GNU toolchain working in other directories ?

Kai Ruottu
Fri Jul 9 05:26:00 GMT 1999

> >   > Is it possible to make it work in any 
> >   > directory with just changing some environment variables ?
> >   > Thanks
> For those who use this technique.  How do you avoid conflict
> with any number of GNU compilers that you might also use
> in the same environment?  i.e. The native GNU C compiler will
> also use this environment variable.

 How can there be conflicts? The native GCC/G++-drivers are named as 'gcc/g++',
the cross-tools as '<target>-gcc/<target>-g++' (or something else -- I use the
names like 'gcc-m68k-coff'...), and the target binaries, libs and headers are 
behind the '../../<target>' and '<target>' from GCC_EXEC_PREFIX... Handling the
native host just as a one target more, will put it into the same hierarchy...

 There are such misuderstandings like putting GNU as and ld, and cc1, cpp etc. 
into the system PATH, so that they can be found....

 I have repeated the advice to use the option '-print-search-dirs' in 
' etc., to see the search paths for a GCC, but still the option is 
mostly unknown to all GCC users... Perhaps all the list members should take 
this as a 'mantra' and try to mention it everywhere... "How many times...the 
answer is flying in the wind..."

 Another option to try with the GNU tools is the '--help' to see the important
options for the command :

   gcc --help
   as --help
   ld --help
   nm --help

 Unfortunately only the egcs-1.1.x and newer has this option available, but to 
get people to think to write '--help', when needing any on-line help for a 
command, would be another thing to repeat...

Cheers, Kai
New CrossGCC FAQ:
To remove yourself from the crossgcc list, send
mail to with the
text 'unsubscribe' (without the quotes) in the
body of the message.

More information about the crossgcc mailing list