On Sat, 21 Sep 2013 14:01:28 -0500 Alexander von Gluck IV <kallisti5@xxxxxxxxxxx> wrote: > On Sat, 21 Sep 2013 20:49:51 +0200 > Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > > > On 09/21/2013 07:13 AM, Alexander von Gluck IV wrote: > > > * The "generated/cross-tools" directory is moved to a > > > tempory directory in /tmp/haiku-crosstools > > > > That is not supported. You generally cannot move gcc/binutils from their > > installation location to a different place and expect them to work. > > It actually does work for everything except the gcc2 images. It's kind > of the same process you use for compiling Haiku under Haiku, you have to > specify the gcc prefix path. Ah-ha... kallisti5@build haiku :) $ /tmp/haiku-crosstools/i586gcc2/bin/i586-pc-haiku-gcc -print-search-dirs install: /home/kallisti5/bamboo/xml-data/build-dir/HAKU-GCC2BT-JOB1/haiku/generated/cross-tools/lib/gcc-lib/i586-pc-haiku/2.95.3-haiku-121101/ programs: /home/kallisti5/bamboo/xml-data/build-dir/HAKU-GCC2BT-JOB1/haiku/generated/cross-tools/lib/gcc-lib/i586-pc-haiku/2.95.3-haiku-121101/:/home/kallisti5/bamboo/xml-data/build-dir/HAKU-GCC2BT-JOB1/haiku/generated/cross-tools/lib/gcc-lib/i586-pc-haiku/:/usr/lib/gcc/i586-pc-haiku/2.95.3-haiku-121101/:/usr/lib/gcc/i586-pc-haiku/:/home/kallisti5/bamboo/xml-data/build-dir/HAKU-GCC2BT-JOB1/haiku/generated/cross-tools/i586-pc-haiku/bin/i586-pc-haiku/2.95.3-haiku-121101/:/home/kallisti5/bamboo/xml-data/build-dir/HAKU-GCC2BT-JOB1/haiku/generated/cross-tools/i586-pc-haiku/bin/ libraries: /home/kallisti5/bamboo/xml-data/build-dir/HAKU-GCC2BT-JOB1/haiku/generated/cross-tools/lib/gcc-lib/i586-pc-haiku/2.95.3-haiku-121101/:/usr/lib/gcc/i586-pc-haiku/2.95.3-haiku-121101/:/home/kallisti5/bamboo/xml-data/build-dir/HAKU-GCC2BT-JOB1/haiku/generated/cross-tools/i586-pc-haiku/lib/i586-pc-haiku/2.95.3-haiku-121101/:/home/kallisti5/bamboo/xml-data/build-dir/HAKU-GCC2BT-JOB1/haiku/generated/cross-tools/i586-pc-haiku/lib/ kallisti5@build haiku :) $ /tmp/haiku-crosstools/i586gcc4/bin/i586-pc-haiku-gcc -print-search-dirs install: /tmp/haiku-crosstools/i586gcc4/bin/../lib/gcc/i586-pc-haiku/4.7.3/ programs: =/tmp/haiku-crosstools/i586gcc4/bin/../libexec/gcc/i586-pc-haiku/4.7.3/:/tmp/haiku-crosstools/i586gcc4/bin/../libexec/gcc/:/tmp/haiku-crosstools/i586gcc4/bin/../lib/gcc/i586-pc-haiku/4.7.3/../../../../i586-pc-haiku/bin/i586-pc-haiku/4.7.3/:/tmp/haiku-crosstools/i586gcc4/bin/../lib/gcc/i586-pc-haiku/4.7.3/../../../../i586-pc-haiku/bin/ libraries: =/tmp/haiku-crosstools/i586gcc4/bin/../lib/gcc/i586-pc-haiku/4.7.3/:/tmp/haiku-crosstools/i586gcc4/bin/../lib/gcc/:/tmp/haiku-crosstools/i586gcc4/bin/../lib/gcc/i586-pc-haiku/4.7.3/../../../../i586-pc-haiku/lib/i586-pc-haiku/4.7.3/:/tmp/haiku-crosstools/i586gcc4/bin/../lib/gcc/i586-pc-haiku/4.7.3/../../../../i586-pc-haiku/lib/ Comparing those two... gcc2 is looking in the hard-coded build directory, gcc4 is smart enough to use its local directories. -- Alex