From: Renegade M. <dra...@sp...> - 2001-09-03 03:34:27
|
Hello. I've been trying to build a cross compiler but so far have had no luck. Following the instructions in the Tools section, binutils installs just fine. But when building gcc, there are problems. Compilation goes for awhile and then i get this: as: unrecognized option `-little' make[2]: *** [libgcc/./_ashiftrt.o] Error 1 make[2]: Leaving directory `/home/build/build-gcc/gcc' make[1]: *** [stmp-multilib] Error 2 make[1]: Leaving directory `/home/build/build-gcc/gcc' make: *** [all-gcc] Error 2 make: Leaving directory `/home/build/build-gcc' I've never tried building a cross compiler before. I'm running a Red Hat 6.2 system. I tried upgrading some of the compilation tools, but i still run into the problem. Here's the versions of some of the tools that i'm using: make - 3.79 gcc - 2.95.3 ar - 2.11.2 Any ideas? Any help would be greatly appreciated. I would really like to be able to build software for my Dreamcast so that i can start developing for it and learn how to port packages to it. -- Dan -------------------------------------------------------------------- "I'm still sane on three planets and two moons." -------------------------------------------------------------------- Daniel Ramaley 3118 Cottage Grove Ave Apt 8 dramaley at spatulacity dot cx Des Moines, Iowa 50311 http://www.spatulacity.cx/ (515) 271-5233 -------------------------------------------------------------------- WARNING: REDISTRIBUTION OF THIS MESSAGE MAY BE IN VIOLATION OF APPLICABLE COPYRIGHT LAWS. THIS MESSAGE NOT GUARANTEED Y-TO-K COMPLIANT. |
From: M. R. B. <mr...@0x...> - 2001-09-03 14:53:40
|
* Renegade Muskrat <dra...@sp...> on Sun, Sep 02, 2001: > Hello. I've been trying to build a cross compiler but so far have had no > luck. Following the instructions in the Tools section, binutils installs > just fine. But when building gcc, there are problems. Compilation goes for > awhile and then i get this: > > as: unrecognized option `-little' > make[2]: *** [libgcc/./_ashiftrt.o] Error 1 > make[2]: Leaving directory `/home/build/build-gcc/gcc' > make[1]: *** [stmp-multilib] Error 2 > make[1]: Leaving directory `/home/build/build-gcc/gcc' > make: *** [all-gcc] Error 2 > make: Leaving directory `/home/build/build-gcc' > Make sure that the cross-compiled binutils is on your PATH after you build them. The error above is from gcc's cross-compiler system not being able to find the cross binutils and falling back on your system (presumably i386-based) assembler. M. R. |
From: Renegade M. <dra...@sp...> - 2001-09-03 15:36:27
|
Thank you for your response. I am using /usr/local/sh-linux as my target directory. I already had /usr/local/sh-linux/bin as the first entry in the PATH. Should i have a different directory in the PATH as well? >Make sure that the cross-compiled binutils is on your PATH after you build >them. The error above is from gcc's cross-compiler system not being able >to find the cross binutils and falling back on your system (presumably >i386-based) assembler. > >M. R. |
From: M. R. B. <mr...@0x...> - 2001-09-03 15:47:09
|
* Renegade Muskrat <dra...@sp...> on Mon, Sep 03, 2001: > > I am using /usr/local/sh-linux as my target directory. I already had > /usr/local/sh-linux/bin as the first entry in the PATH. Should i have a > different directory in the PATH as well? > Hmm, no that should be correct. Could you post your configure command lines for binutils and gcc? M. R. |
From: Renegade M. <dra...@sp...> - 2001-09-04 01:34:23
|
>> I am using /usr/local/sh-linux as my target directory. I already had >> /usr/local/sh-linux/bin as the first entry in the PATH. Should i have a >> different directory in the PATH as well? > >Hmm, no that should be correct. Could you post your configure command >lines for binutils and gcc? Here is the complete list of commands that i have run so far. If it would help to see the output of the configure and make commands, i can post them to a web page upon request. Anything i'm doing wrong here? HOST=i686-pc-linux-gnu TARGET=sh-linux BASE=/home/build PREFIX=/usr/local/${TARGET} PATH=${PREFIX}/bin:${PATH} # binutils cd ${BASE} tar -xvIf binutils-010513.tar.bz2 gunzip -c sh-binutils-010513-rela+arch+opc.diff.gz | patch -p0 mkdir build-binutils cd build-binutils ../binutils-010513/configure --target=${TARGET} --prefix=${PREFIX} -v \ 2>&1 | tee -a configure.out make -w all install \ 2>&1 | tee -a make.out # gcc cd ${BASE} tar -xvIf gcc-core-20010514.tar.bz2 tar -xvIfgcc-g++-20010514.tar.bz2 gunzip -c sh-gcc-20010514-arch+pic+wind+misc.diff.gz | patch -p0 mkdir build-gcc cd build-gcc ../gcc-20010514/configure --host=${HOST} --target=${TARGET} \ --without-headers --with-newlib -v \ 2>&1 | tee -a configure.out make -w all-gcc install-gcc \ 2>&1 | tee -a make.out |
From: M. R. B. <mr...@0x...> - 2001-09-04 02:16:58
|
* Renegade Muskrat <dra...@sp...> on Mon, Sep 03, 2001: > TARGET=sh-linux > BASE=/home/build > PREFIX=/usr/local/${TARGET} > PATH=${PREFIX}/bin:${PATH} > [...] > > # gcc > > cd ${BASE} > tar -xvIf gcc-core-20010514.tar.bz2 > tar -xvIfgcc-g++-20010514.tar.bz2 > gunzip -c sh-gcc-20010514-arch+pic+wind+misc.diff.gz | patch -p0 > mkdir build-gcc > cd build-gcc > ../gcc-20010514/configure --host=${HOST} --target=${TARGET} \ > --without-headers --with-newlib -v \ > 2>&1 | tee -a configure.out You forgot --prefix=${PREFIX} here. M. R. |