From: Arthur Haas <ahaas@impactweather.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: Bootstrap failures on i386-pc-solaris2.10
Date: Thu, 01 Apr 2010 14:38:00 -0000 [thread overview]
Message-ID: <DFE02D10614AD44A85D2986AB72F66E90535100923@ATLANTIS.impactweather.local> (raw)
In-Reply-To: <yddoci3i72v.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
I'll update my repo shortly and replace the '--with-arch' and '--with-tune' arguments as you suggest. As for the '--disable-libstdcxx-pch'
argument, I had build problems months ago and this argument fixed the problem, although now looking at the configure script for libstdc
it looks like the correct argument should be '--enable-libstdcxx-pch=no' if it is to be used. The '--enable-threads' argument is another configuration option I added long ago as well. The script which configures and starts my GCC builds needs some cleanup ...
Thanks.
Art Haas
-----Original Message-----
From: Rainer Orth [mailto:ro@CeBiTec.Uni-Bielefeld.DE]
Sent: Thursday, April 01, 2010 9:25 AM
To: Arthur Haas
Cc: gcc@gcc.gnu.org
Subject: Re: Bootstrap failures on i386-pc-solaris2.10
Hi Art,
> 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 ...
The --disable-multilib option has been broken by a recent patch. This
is a known bug and will hopefully be fixed soon.
Configuring with --with-arch=pentium4 --with-tune=pentium4 is wrong and
doesn't work in the general case, as you've discovered, since it breaks
the 64-bit support. You just didn't notice the problem before due to
--disable-multilib. Use --with-arch_32=pentium4 --with-tune_32=pentium4
instead, or simply update to current mainline: my patch to default the
i?86-*-solaris2* configurations to pentium4 just went in.
As for the other configure options: --enable-threads is superfluous,
it's the default. What are you trying to achieve with
--disable-libstdcxx-pch?
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2010-04-01 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 14:14 Art Haas
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 [this message]
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=DFE02D10614AD44A85D2986AB72F66E90535100923@ATLANTIS.impactweather.local \
--to=ahaas@impactweather.com \
--cc=gcc@gcc.gnu.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).