From: Art Haas <ahaas@impactweather.com>
To: gcc@gcc.gnu.org
Subject: Bootstrap failures on i386-pc-solaris2.10
Date: Thu, 01 Apr 2010 14:14:00 -0000 [thread overview]
Message-ID: <201004011414.o31EE6Eu001210@impdell3.impactweather.local> (raw)
Hi.
My builds on my X86 solaris box have failed since yesterday, and
I've just found bug 43615 in Bugzilla which indicates a different
but similar issue for an x86-64 build.I'm running Solaris 10 on an
older Dell box with a Pentium4 chip, and have been building
gcc with the '--disable-multilib' argument for quite some time.
Here's the config info from the last build which worked:
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/export/home/arth/local/libexec/gcc/i386-pc-solaris2.10/4.5.0/lto-wrapper
Target: i386-pc-solaris2.10
Configured with: /home/ahaas/gnu/gcc.git/configure --prefix=/export/home/arth/local --enable-languages=c,c++,objc,fortran --disable-nls --with-gmp=/export/home/arth/local --with-mpfr=/export/home/arth/local --enable-checking=release --enable-threads --with-gnu-as --with-as=/export/home/arth/local/bin/as --with-gnu-ld --with-ld=/export/home/arth/local/bin/ld --disable-multilib --disable-libstdcxx-pch --enable-objc-gc --build=i386-pc-solaris2.10 --with-arch=pentium4 --with-tune=pentium4
Thread model: posix
gcc version 4.5.0 20100330 (experimental) (GCC)
Here's the last bits of today's build log - the '--disable-multilib' configure
option should have skipped the 'amd64' stuff below ...
config.status: executing default commands
Adding multilib support to Makefile in /home/ahaas/gnu/gcc.git/libgcc
multidirs=amd64
with_multisubdir=
Running configure in multilib subdirs amd64
pwd: /export/home/arth/gnu/gcc-0401/i386-pc-solaris2.10/libgcc
Running configure in multilib subdir amd64
pwd: /export/home/arth/gnu/gcc-0401/i386-pc-solaris2.10
mkdir amd64
configure: creating cache ./config.cache
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /export/home/arth/local/bin/ginstall -c
checking for gawk... gawk
checking build system type... i386-pc-solaris2.10
checking host system type... i386-pc-solaris2.10
checking for i386-pc-solaris2.10-ar... /export/home/arth/local/i386-pc-solaris2.10/bin/ar
checking for i386-pc-solaris2.10-lipo... lipo
checking for i386-pc-solaris2.10-nm... /export/home/arth/gnu/gcc-0401/./gcc/nm
checking for i386-pc-solaris2.10-ranlib... /export/home/arth/local/i386-pc-solaris2.10/bin/ranlib
checking for i386-pc-solaris2.10-strip... /export/home/arth/local/i386-pc-solaris2.10/bin/strip
checking whether ln -s works... yes
checking for i386-pc-solaris2.10-gcc... /export/home/arth/gnu/gcc-0401/./gcc/xgcc -B/export/home/arth/gnu/gcc-0401/./gcc/ -B/export/home/arth/local/i386-pc-solaris2.10/bin/ -B/export/home/arth/local/i386-pc-solaris2.10/lib/ -isystem /export/home/arth/local/i386-pc-solaris2.10/include -isystem /export/home/arth/local/i386-pc-solaris2.10/sys-include -m64
checking for suffix of object files... configure: error: in `/export/home/arth/gnu/gcc-0401/i386-pc-solaris2.10/amd64/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Error 1
make[2]: Leaving directory `/export/home/arth/gnu/gcc-0401'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/export/home/arth/gnu/gcc-0401'
make: *** [bootstrap-lean] Error 2
The 'config.log' file from the 'i386-pc-solaris2.10/amd64/libgcc' directory
fails with errors regard the x86-64 instructions ...
configure:3211: checking for suffix of object files
configure:3233: /export/home/arth/gnu/gcc-0401/./gcc/xgcc -B/export/home/arth/gnu/gcc-0401/./gcc/ -B/export/home/arth/local/i386-pc-solaris2.10/bin/ -B/export/home/arth/local/i386-pc-solaris2.10/lib/ -isystem /export/home/arth/local/i386-pc-solaris2.10/include -isystem /export/home/arth/local/i386-pc-solaris2.10/sys-include -m64 -c -g -O2 conftest.c >&5
conftest.c:1:0: error: CPU you selected does not support x86-64 instruction set
conftest.c:1:0: error: CPU you selected does not support x86-64 instruction set
configure:3237: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "GNU C Runtime Library"
| #define PACKAGE_TARNAME "libgcc"
| #define PACKAGE_VERSION "1.0"
| #define PACKAGE_STRING "GNU C Runtime Library 1.0"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL "http://www.gnu.org/software/libgcc/"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3251: error: in `/export/home/arth/gnu/gcc-0401/i386-pc-solaris2.10/amd64/libgcc':
configure:3254: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
My builds on a sparc-sun-solaris2.10 from yesterday worked fine - on
this machine GCC does _not_ use the '--disable-multilib' configuration
switch. This mornings build has just started.
My thanks to everyone working on GCC.
Art Haas
next reply other threads:[~2010-04-01 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 14:14 Art Haas [this message]
2010-04-01 14:23 ` H.J. Lu
2010-04-01 14:43 ` Rainer Orth
2010-04-01 14:24 ` Rainer Orth
2010-04-01 14:38 ` Arthur Haas
2010-04-06 18:26 ` Rainer Orth
2010-04-01 16:13 ` Arthur Haas
2010-04-01 16:38 ` Ralf Wildenhues
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004011414.o31EE6Eu001210@impdell3.impactweather.local \
--to=ahaas@impactweather.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).