This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tue, 9 Nov 2004, Dan Kegel wrote: > Robert P. J. Day wrote: > > > > i then copied all of .../gcc-3.4.1-glibc-2.3.3/ to /usr/local/sh3, > > > > and reset my PATH to instead include /usr/local/sh3/bin. ran same > > > > test compiles, got the same output. i realize this doesn't constitute > > > > a rigorous test, but it seems promising. (once i read more, i'll > > > > probably realize that i didn't need to copy *everything* from that > > > > results directory over to /usr/local/sh3 but better safe than sorry). > > > > > > Well, that depends... did you *copy* everything or did you *move* the > > > tree? > > > > > > "cp -a" since it was in a different filesystem. is that a problem? > > The copied toolchain has hardcoded paths to the old location, so > what you did is no test at all. You need to rename the old one so > that the hardcoded paths are invalid, and see if the new copy still > works. 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? rday ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |