RE: Problem with pathing crt1.o in crosstool

["Michael Miller" <michael dot miller at prga dot com>]

Mike wrote:
>> I setup the environment variables as:
>>
>> ccpath=/opt/crosstool/gcc-3.4.4-glibc-2.3.5/arm-xscale-linux-gnu
>> export GCC_EXEC_PREFIX=$ccpath/lib/
>> export
C_INCLUDE_PATH=$ccpath/include/:$ccpath/lib/gcc/arm-xscale-linux-gnu/3.4.4/i
nclude/:$ccpath/arm-xscale-linux-gnu/include/
>> export CPLUS_INCLUDE_PATH=$C_INCLUDE_PATH
>> export INFOPATH=$ccpath/info
>> export LIBRARY_PATH=$ccpath/lib/gcc/arm-xscale-linux-gnu/3.4.4
>> export COMPILER_PATH=$ccpath/bin/:$ccpath/arm-xscale-linux-gnu/bin/
>> export PATH=$ccpath/bin:$ccpath/arm-xscale-linux-gnu/bin:$PATH
>> export MACHTYPE=arm-xscale-linux-gnu

Dan wrote:
>Yikes.  I think never do any of that crap.  Instead, I just set
>CROSS_COMPILE to an absolute prefix, e.g.
>CROSS_COMPILE=/opt/crosstool/gcc-3.4.4-glibc-2.3.5/arm-xscale-linux->gnu/bi
n/arm-xscale-linux-gnu-

Mike wrote:
>> Do I need to tweak the specs before I build the tool chain so that it
points to my final destination under /opt/crosstool?

Dan wrote:
>Lord, no.  You're making things too hard, I think...
>- Dan

You actually made me laugh out loud.  You are (as usual) correct.  Not
messing with any environment variables or paths caused everything to build
correctly.

	Much thanks,
	Mike


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org