public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: crossgcc@sourceware.org
Subject: gold vs. CT_STATIC_TOOLCHAIN
Date: Fri, 02 Dec 2011 13:25:00 -0000	[thread overview]
Message-ID: <20111202132450.GA24105@sig21.net> (raw)

Hi,

with CT_STATIC_TOOLCHAIN ./scripts/build/binutils/binutils.sh
adds -all-static to LDFLAGS.  However, -all-static is a libtool
option and gold is not libtoolized.  Maybe cg-ng should just
disable gold when CT_STATIC_TOOLCHAIN is selected?

Untested:  (the 2nd and 3rd hunk are actually a seperate bugfix)


diff -r cf509170838f config/binutils/binutils.in
--- a/config/binutils/binutils.in	Wed Nov 30 12:07:59 2011 +0100
+++ b/config/binutils/binutils.in	Fri Dec 02 14:21:20 2011 +0100
@@ -101,6 +101,9 @@
 config BINUTILS_FORCE_LD_BFD
     bool
 
+config STATIC_TOOLCHAIN
+    select BINUTILS_FORCE_LD_BFD
+
 choice
     bool
     prompt "Linkers to enable"
@@ -130,6 +133,7 @@
     prompt "ld, gold"
     depends on BINUTILS_HAS_GOLD
     depends on BINUTILS_GOLD_SUPPORTS_ARCH
+    depends on ! BINUTILS_FORCE_LD_BFD
     depends on EXPERIMENTAL
     select BINUTILS_GOLD_INSTALLED
     select BINUTILS_LINKER_BOTH
@@ -144,6 +148,7 @@
     prompt "gold, ld"
     depends on BINUTILS_HAS_GOLD
     depends on BINUTILS_GOLD_SUPPORTS_ARCH
+    depends on ! BINUTILS_FORCE_LD_BFD
     depends on EXPERIMENTAL
     select BINUTILS_GOLD_INSTALLED
     select BINUTILS_LINKER_BOTH


Johannes

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2011-12-02 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 13:25 Johannes Stezenbach [this message]
2011-12-13 17:23 ` Johannes Stezenbach
2011-12-13 22:32   ` Yann E. MORIN
2011-12-14  0:09 ` Yann E. MORIN
2011-12-14 11:15   ` Johannes Stezenbach
2011-12-14 11:43     ` Johannes Stezenbach
2012-01-16 23:22       ` Yann E. MORIN
2012-01-18 12:01         ` Johannes Stezenbach

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=20111202132450.GA24105@sig21.net \
    --to=js@sig21.net \
    --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).