public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Top-level build machinery patch ping (Was: Re: [gccgo] Use -static-libstdc++ when building the Go compiler)
Date: Sat, 21 Nov 2009 01:54:00 -0000	[thread overview]
Message-ID: <mcrhbso4ptw.fsf_-_@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0911210020180.4910@digraph.polyomino.org.uk> (Joseph S. Myers's message of "Sat\, 21 Nov 2009 00\:24\:54 +0000 \(UTC\)")

"Joseph S. Myers" <joseph@codesourcery.com> writes:

> On Fri, 20 Nov 2009, Ian Lance Taylor wrote:
>
>> When bootstrapping gccgo, the Go compiler winds up being built with
>> the current version of libstdc++.  That makes it a pain to run if the
>> current version of libstdc++ is newer than the system version.
>> Fortunately I introduced the -static-libstdc++ option to avoid just
>> this issue for the build-with-cxx branch.  This patch uses the option,
>> if it is supported, when building the Go compiler.  Committed to gccgo
>> branch.
>
> This should not override --with-host-libstdcxx (and my previous comments 
> <http://gcc.gnu.org/ml/gcc-patches/2009-06/msg01719.html> that C++ code 
> should be linked with $(CC) in non-bootstrapped builds with 
> --with-host-libstdcxx apply equally here as they do to building the whole 
> compiler as C++ - i.e. things to get right before merging the Go compiler 
> to trunk, or building the whole compiler as C++ by default).

Speaking of your previous comments, I don't think anybody ever
reviewed 

http://gcc.gnu.org/ml/gcc-patches/2009-06/msg01930.html

So: ping.

Ian

  reply	other threads:[~2009-11-21  1:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-21  0:04 [gccgo] Use -static-libstdc++ when building the Go compiler Ian Lance Taylor
2009-11-21  0:54 ` Joseph S. Myers
2009-11-21  1:54   ` Ian Lance Taylor [this message]
2009-11-21  2:46     ` Top-level build machinery patch ping (Was: Re: [gccgo] Use -static-libstdc++ when building the Go compiler) DJ Delorie
2009-11-21  9:44       ` Paolo Bonzini

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=mcrhbso4ptw.fsf_-_@dhcp-172-17-9-151.mtv.corp.google.com \
    --to=iant@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    /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).