This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Problems building gcc-3.1.1 on 32-bit sparc-sun-solaris2.7
- From: Kick Damien-DKICK1 <DKICK1 at motorola dot com>
- To: "'gcc-help at gcc dot gnu dot org'" <gcc-help at gcc dot gnu dot org>
- Cc: Kick Damien-DKICK1 <DKICK1 at motorola dot com>
- Date: Tue, 30 Jul 2002 16:36:16 -0500
- Subject: Problems building gcc-3.1.1 on 32-bit sparc-sun-solaris2.7
I'm having problems building gcc-3.1.1 on a 32-bit
sparc-sun-solaris2.7.
checking whether the C compiler
(/usr/test/awo/user_work/kick/obj/sparc-sun-solaris2.7-32/gcc-3.1.1/gcc/xgcc
-B/usr/test/awo/user_work/kick/obj/sparc-sun-solaris2.7-32/gcc-3.1.1/gcc/
-B/usr/test/awo/user_work/kick/sparc-sun-solaris2.7-32/sparc-sun-solaris2.7/
bin/
-B/usr/test/awo/user_work/kick/sparc-sun-solaris2.7-32/sparc-sun-solaris2.7/
lib/ -isystem
/usr/test/awo/user_work/kick/sparc-sun-solaris2.7-32/sparc-sun-solaris2.7/in
clude -m64 -g -O2 ) works... no
configure: error: installation or configuration problem: C compiler
cannot create executables.
make[1]: *** [configure-target-libiberty] Error 1
make[1]: Leaving directory
`/usr/test/awo/user_work/kick/obj/sparc-sun-solaris2.7-32/gcc-3.1.1'
make: *** [bootstrap] Error 2
[kick@csdndev07 sparc-sun-solaris2.7-32/gcc-3.1.1]% isainfo -v
32-bit sparc applications
[kick@csdndev07 sparc-sun-solaris2.7-32/gcc-3.1.1]% cat
config.status
#!/bin/sh
# This file was generated automatically by configure. Do not edit.
# This directory was configured as follows:
../../../src/gcc-3.1.1/configure
--with-gcc-version-trigger=/usr/test/awo/user_work/kick/src/gcc-3.1.1/gcc/ve
rsion.c --host=sparc-sun-solaris2.7
--prefix=/usr/test/awo/user_work/kick/sparc-sun-solaris2.7-32
--with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --enable-languages=c,c++
--norecursion
# using "mh-frag"
[kick@csdndev07 sparc-sun-solaris2.7-32/gcc-3.1.1]%
I'm assuming that the problem is from the '.../xgcc ... -m64 ...' as
the box has not been enabled for 64-bit applicaitons. Does this sound
reasonable? Why is 'configure' assuming that I want 64-bit? Is there
an option that I can pass to 'configure' to explicitly request '-m32'?
--
Damien Kick