From: Ian Lance Taylor <iant@google.com>
To: binutils@sourceware.org
Subject: Patch committed: Merge from gcc top level
Date: Tue, 07 Dec 2010 21:21:00 -0000 [thread overview]
Message-ID: <mcrwrnlnutj.fsf@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
I merged this patch from gcc top level to binutils mainline.
Ian
2010-12-02 Ian Lance Taylor <iant@google.com>
* configure.ac: Always set default for poststage1_ldflags to
-static-libstdc++ -static-libgcc.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: foo.patch --]
[-- Type: text/x-diff, Size: 950 bytes --]
Index: configure.ac
===================================================================
RCS file: /cvs/src/src/configure.ac,v
retrieving revision 1.119
diff -u -r1.119 configure.ac
--- configure.ac 6 Dec 2010 01:55:25 -0000 1.119
+++ configure.ac 7 Dec 2010 21:19:56 -0000
@@ -1561,10 +1561,10 @@
poststage1_ldflags=$withval
fi],
[poststage1_ldflags=
- # With --enable-build-with-cxx, default to linking libstdc++ and
- # libgcc statically. But if the user explicitly specified the
- # libraries to use, trust that they are doing what they want.
- if test "$ENABLE_BUILD_WITH_CXX" = "yes" -a "$poststage1_libs" = ""; then
+ # In stages 2 and 3, default to linking libstdc++ and libgcc
+ # statically. But if the user explicitly specified the libraries to
+ # use, trust that they are doing what they want.
+ if test "$poststage1_libs" = ""; then
poststage1_ldflags="-static-libstdc++ -static-libgcc"
fi])
AC_SUBST(poststage1_ldflags)
reply other threads:[~2010-12-07 21:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mcrwrnlnutj.fsf@google.com \
--to=iant@google.com \
--cc=binutils@sourceware.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).