Re: some problem about cross-compile the gcc-2.95.3

["Kai Ruottu" <karuottu at mbnet dot fi>]

On 16 Apr 2005 at 7:48, Dan Kegel wrote:

> zouq wrote:
>
> first i download the release the version of gcc-2.95.3, binutils
> 2.15, and i use the o32 lib, include of gcc3.3.3 .

 Please elaborate this!  What is the target, why you need just
this 'o32' C library?  Is gcc-3.3.3 the current production GCC on the
'native' system or on some existing crosstoolchain?  Has your
gcc-2.95.3 any extra patches for it?  I remember gcc-2.95.3
needing patches for just MIPS, but maybe it was SVR4.2/MIPS
(big-endian) which required them...

 Also the workability of gcc-3.3.x with 'mipsel-linux' is somehow
unclear....  It can be that both gcc-3.2 and 3.3 could produce bad
code, the quite current binutils-2.15.94.0.2.2 claimed this.

> 3. compile the gcc
> export PATH=$PATH:/opt/gcc/bin
> mkdir gcc-build;
> cd gcc-build;
> .../../gcc-2.95.3/configure --prefix=/opt/gcc --target=mipsel-linux

 Using the '--prefix=/opt/gcc' is claimed here...

>  /home/mytask/mywork/WHAT_I_HAVE_DONE/mycompile/gcc-2.95.3-
build/gcc/gcc/xgcc
> -B/home/mytask/mywork/WHAT_I_HAVE_DONE/mycompile/gcc-2.95.3-
build/gcc/gcc/
> -B=/opt/gcc-2.95//mipsel-linux/bin/
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

 But this -B option clearly tells that '--prefix=/opt/gcc-2.95/' was
used when configuring GCC !!!!

>  -I=/opt/gcc-2.95//mipsel-linux/include

 Also this option tells the same fact....  One cannot lie with these
things. Maybe a reconfigure happened without cleaning first the
old stuff from earlier configure or something but the shown $prefix,
 '/opt/gcc-2.95/',  cannot appear from nowhere...

> > as: unrecognized option `-O2'
> 
> I already told you: you probably need
> to put the directory containing
> the bin of the binutils you built
> on the PATH before configuring gcc.

 That was done by Zouq...

 Using the same $prefix during the binutils and
GCC configures was the clue here... As seen,
Zouq used different $prefix'es although claiming
using just the same...

 GCC searches only "as", not "mipsel-linux-as",
so although putting the '$prefix/bin' into PATH is
obligatory, it doesn't help much GCC itself, only
the configure scripts and Makefiles.


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