This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: some compile problem about gcc-2.95.3
- From: Kai Ruottu <karuottu at mbnet dot fi>
- To: zouqiong <zouqiong at ict dot ac dot cn>
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 19 Jun 2005 23:58:58 +0300
- Subject: Re: some compile problem about gcc-2.95.3
- References: <1113549393.28652.5.camel@godson>
- Reply-to: karuottu at mbnet dot fi
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...