From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Arthur Haas <ahaas@impactweather.com>
Cc: "gcc\@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Bootstrap failures on i386-pc-solaris2.10
Date: Tue, 06 Apr 2010 18:26:00 -0000 [thread overview]
Message-ID: <yddr5msh1zv.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <DFE02D10614AD44A85D2986AB72F66E90535100923@ATLANTIS.impactweather.local> (Arthur Haas's message of "Thu, 1 Apr 2010 09:38:12 -0500")
Arthur Haas <ahaas@impactweather.com> writes:
> 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 ...
No, --enable-<feature>=no and --disable-<feature> should be equivalent
everywhere, even if only one form is documented.
True: one you have something that works, you seldom revisit it ;-)
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2010-04-06 18:26 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
2010-04-06 18:26 ` Rainer Orth [this message]
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=yddr5msh1zv.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=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).