Re: relocating the compiler and associated tools

[Dan Kegel <dank at kegel dot com>]

Robert P. J. Day wrote:
> i realize that i didn't mention in my earlier email, i did in fact
> rename the old "result" directory out of the way.  but here's what i
> just did:  after generating the entire results directory in one place,
> i copied the entire directory to /usr/local/sh3/.
>
> i then went into that directory, to bin/gcc, and ran the following:
>
> $ strings *gcc | grep result
> /home/rpjday/ct/crosstool-0.28-rc37/build/sh3-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.3/gcc-3.4.1/configure
> --target=sh3-unknown-linux-gnu --host=i686-host_pc-linux-gnu
> --prefix=/home/rpjday/ct/result/sh3-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.3
> --with-headers=/home/rpjday/ct/result/sh3-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.3/sh3-unknown-linux-gnu/include
> --with-local-prefix=/home/rpjday/ct/result/sh3-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.3/sh3-unknown-linux-gnu
> --disable-nls --enable-threads=posix --enable-symvers=gnu
> --enable-__cxa_atexit --enable-languages=c,c++ --enable-shared
> --enable-c99 --enable-long-long
> /home/rpjday/ct/result/sh3-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.3/lib/gcc/
> /home/rpjday/ct/result/sh3-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.3/bin/
> /home/rpjday/ct/result/sh3-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.3/libexec/gcc/
> /home/rpjday/ct/result/sh3-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.3
>
>   in short, i searched strings in the cross-compile gcc for part of
> the name of the original result directory, and note at the bottom, the
> four lines that reflect the *original* result directory.  sorry, i
> don't know what those lines represent, but obviously, there's a memory
> of the original result location in the gcc executable.
>
>   is this what people were curious about?

That, and whether those hardcoded paths actually get used.
Please do
/usr/local/sh3/bin/sh3-unknown-linux-gnu-gcc --print-file-name crt1.o
/usr/local/sh3/bin/sh3-unknown-linux-gnu-gcc --print-file-name specs
and let's see where it finds those two files.
If it finds them in the new location, great, the relocation is
basically working... but who knows what other files it might
accidentally find in the old place instead.  The only way
to find out would be to really use the toolchain for a while
with the old paths invalidated.
- Dan

--
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html

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