some compile problem about gcc-2.95.3

some compile problem about gcc-2.95.3

[zouqiong]

i download the release version of gcc-2.95.3, and binutils 2.15, then i
did the following things:
1.
mkdir binutils-build;

../../binutils-2.15/configure --prefix=/opt/gcc --target=mipsel-linux
-v;

make;make install;

2.i copy the o32 lib, o32 include to the /opt/gcc/mipsel-linux/lib,
/opt/gcc/mipsel-linux/include,

3.
mkdir gcc-build;
 
../../gcc-2.95.3/configure --prefix=/opt/gcc --target=mipsel-linux
--enable-languages=c --disable-checking -enable-shared -v;
 
 make;

 then errors go like this:
for name in _muldi3 _divdi3 _moddi3 _udivdi3 _umoddi3 _negdi2 _lshrdi3
_ashldi3 _ashrdi3 _ffsdi2 _udiv_w_sdiv _udivmoddi4 _cmpdi2 _ucmpdi2
_floatdidf _floatdisf _fixunsdfsi _fixunssfsi _fixunsdfdi _fixdfdi
_fixunssfdi _fixsfdi _fixxfdi _fixunsxfdi _floatdixf _fixunsxfsi
_fixtfdi _fixunstfdi _floatditf __gcc_bcmp _varargs __dummy _eprintf _bb
_shtab _clear_cache _trampoline __main _exit _ctors _pure; \
do \
  echo ${name}; \
 
/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/ -I=/opt/gcc-2.95//mipsel-linux/include  -DCROSS_COMPILE -DIN_GCC      -I./include     -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I/usr/include   -I. -I../../../gcc-2.95.3/gcc -I../../../gcc-2.95.3/gcc/config -I../../../gcc-2.95.3/gcc/../include -c -DL${name} \
       ../../../gcc-2.95.3/gcc/libgcc2.c -o ${name}.o; \
  if [ $? -eq 0 ] ; then true; else exit 1; fi; \
  mipsel-linux-ar rc tmplibgcc2.a ${name}.o; \
  rm -f ${name}.o; \
done
_muldi3
as: unrecognized option `-O2'
make[1]: *** [libgcc2.a] Error 1
make[1]: Leaving directory
`/home/mytask/mywork/WHAT_I_HAVE_DONE/mycompile/gcc-2.95.3-build/gcc/gcc'
make: *** [all-gcc] Error 2

i am surprised about it. 

Re: some compile problem about gcc-2.95.3

[Steven J. Hill]

zouqiong wrote:
> 
> i am surprised about it. 
>
You seem surprised, and I am terrified you are using a compiler that
old. Please go look at:

    http://kegel.com/crosstool/

which automatically builds cross toolchains and even still has
scripts to build your ancient (IMHO) combination.

-Steve

Re: some compile problem about gcc-2.95.3

[Kai Ruottu]

Steven J. Hill kirjoitti:

> zouqiong wrote in 15.4.2005 10:16:
>
 > i download the release version of gcc-2.95.3, and binutils 2.15,
 > then i did the following things:
 > 1. mkdir binutils-build;
 > .../../binutils-2.15/configure --prefix=/opt/gcc
 > --target=mipsel-linux -v;
 > make;make install;
 >
 > 2.i copy the o32 lib, o32 include to the /opt/gcc/mipsel-linux/lib,
 > /opt/gcc/mipsel-linux/include,
 >
 > 3. mkdir gcc-build;
 > .../../gcc-2.95.3/configure --prefix=/opt/gcc --target=mipsel-linux
 > --enable-languages=c --disable-checking -enable-shared -v;
 >
>> i am surprised about it.

  I am surprised where this message lied since 15.4.2005 before appearing
now...

> You seem surprised, and I am terrified you are using a compiler that
> old. Please go look at:
> 
>    http://kegel.com/crosstool/
> 
> which automatically builds cross toolchains and even still has
> scripts to build your ancient (IMHO) combination.

... but much more I am surprised why anyone here could advice people,
who would like to get petrol to their old custom ancient cars, to get
gasoline and a modern fully standard car (but self-built from standard
parts) where to use that gasoline...

Re: some compile problem about gcc-2.95.3

[Kai Ruottu]

zouqiong kirjoitti:

> .../../gcc-2.95.3/configure --prefix=/opt/gcc --target=mipsel-linux
> --enable-languages=c --disable-checking -enable-shared -v;

  This is not true at all !!!!

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

  Because these rows tell that a '--prefix=/opt/gcc-2.95/' was used !!!!

> as: unrecognized option `-O2'

  The assembler, 'as', was tried to be used from the chosen
'$prefix/$target/bin', here '/opt/gcc-2.95//mipsel-linux/bin/', but not 
  found from it.

> i am surprised about it. 

  I'm not... Using different $prefix values in the binutils configure and
the GCC configure is a quite common newbie mistake... Maybe because some
people really believe GCC being a human being and therefore having the
'$target-as' and '$target-ld' being in PATH being enough... The opsys
will find them when a human being uses them, so also GCC must find them
or how?

  Those who have opened the GCC manual or tried the '-print-search-dirs'
option with GCC, don't believ anything like that...