From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] ed21bc: binutils: Fix LDFLAGS for static toolchain
Date: Mon, 07 Dec 2015 19:26:00 -0000 [thread overview]
Message-ID: <5665dd7b53b97_27e73fca3a1292bc6843b@hookshot-fe5-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: ed21bcaf8995aa5aad0a9631062ca5e1708e6bdc
https://github.com/crosstool-ng/crosstool-ng/commit/ed21bcaf8995aa5aad0a9631062ca5e1708e6bdc
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2015-12-07 (Mon, 07 Dec 2015)
Changed paths:
M scripts/build/binutils/binutils.sh
Log Message:
-----------
binutils: Fix LDFLAGS for static toolchain
If building a static toolchain, the ldflags option passed to
do_binutils_backend is overridden when we set `LDFLAGS=-all-static`.
We should pass `LDFLAGS=${ldflags} -all-static` in this case.
This fixes #297
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Commit: 8a87716fbfe1743ac4fecd11d5f31e02bbdcbe77
https://github.com/crosstool-ng/crosstool-ng/commit/8a87716fbfe1743ac4fecd11d5f31e02bbdcbe77
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2015-12-07 (Mon, 07 Dec 2015)
Changed paths:
M scripts/build/binutils/binutils.sh
Log Message:
-----------
Merge pull request #299 from bhundven/fix_static_binutils
binutils: Fix LDFLAGS for static toolchain
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/c92387e2a8e2...8a87716fbfe1
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2015-12-07 19:26 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=5665dd7b53b97_27e73fca3a1292bc6843b@hookshot-fe5-cp1-prd.iad.github.net.mail \
--to=bryanhundven@gmail.com \
--cc=crossgcc@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).