public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: Matthias Klose <doko@ubuntu.com>
Cc: Nick Clifton <nickc@redhat.com>,
	 Mark Mitchell <mark@codesourcery.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
	 "H.J. Lu" <hjl.tools@gmail.com>,
	Ian Lance Taylor <iant@google.com>,
	 GCC Patches <gcc-patches@gcc.gnu.org>,
	binutils <binutils@sourceware.org>
Subject: Re: Review of --enable-gold=both patch
Date: Fri, 29 Oct 2010 15:00:00 -0000	[thread overview]
Message-ID: <4CCAE168.2080902@gnu.org> (raw)
In-Reply-To: <4CCAE033.3010009@ubuntu.com>

On 10/29/2010 04:54 PM, Matthias Klose wrote:
>
> to summarize:
>
> - in binutils, --with-default-linker= should trigger which linker is
>    built, and should determine which linker the ld symlink points to.
>
> - if both linkers are built, the non-default linker build has to be
>    enabled with either --enable-ld or --enable-gold.
>
> - values (other than yes or no) passed to --enable-ld and --enable-gold
>    are ignored.
>
> Is this the consensus?

Looks good, except that I'd use --enable-default-linker (it's an 
optional "feature", not an optional "package").

Paolo

  reply	other threads:[~2010-10-29 15:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C27E695.9070802@codesourcery.com>
     [not found] ` <4C286200.30402@gnu.org>
     [not found]   ` <Pine.LNX.4.64.1006281009290.17565@digraph.polyomino.org.uk>
     [not found]     ` <4C2886C7.4040408@gnu.org>
     [not found]       ` <4C28CA2A.7060703@codesourcery.com>
     [not found]         ` <4C28CE9C.9030809@gnu.org>
     [not found]           ` <4C28D9F1.6030309@codesourcery.com>
2010-10-27 14:04             ` Matthias Klose
2010-10-29  9:21               ` Nick Clifton
2010-10-29 14:55                 ` Matthias Klose
2010-10-29 15:00                   ` Paolo Bonzini [this message]
2010-10-29 15:12                   ` Paolo Bonzini
2010-10-29 15:41                     ` Matthias Klose
2010-10-29 15:42                       ` Paolo Bonzini
2010-11-01 20:21                       ` Ralf Wildenhues
2010-11-11  0:09                     ` Matthias Klose
2010-11-11  8:37                       ` Paolo Bonzini
2010-11-12 18:45                         ` Matthias Klose
2010-11-12 19:36                           ` Paolo Bonzini
     [not found]                         ` <4CDD8B19.3040909__3908.7257617668$1289587526$gmane$org@ubuntu.com>
2010-11-12 20:37                           ` Andreas Schwab
2010-11-13 20:04                         ` Matthias Klose
2010-11-13 20:48                           ` Paolo Bonzini
     [not found]                         ` <4CDEEEEB.2000905__41684.8152097829$1289678668$gmane$org@ubuntu.com>
2010-11-14  7:25                           ` Ryan Hill
2010-11-23 12:24                       ` Nick Clifton
2010-11-23 13:27                         ` Matthias Klose
2010-11-23 13:31                           ` Tristan Gingold
2010-11-23 17:09                           ` H.J. Lu
2010-11-23 18:02                             ` H.J. Lu
2010-11-24 10:00                               ` Tristan Gingold
2010-11-24 13:11                                 ` H.J. Lu
2010-11-24 13:25                                   ` Tristan Gingold
2010-11-23 18:13                             ` H.J. Lu

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=4CCAE168.2080902@gnu.org \
    --to=bonzini@gnu.org \
    --cc=binutils@sourceware.org \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=iant@google.com \
    --cc=joseph@codesourcery.com \
    --cc=mark@codesourcery.com \
    --cc=nickc@redhat.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).