public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	binutils@sourceware.org, gcc@gcc.gnu.org
Subject: Re: PATCH: Support --enable-gold=both --with-linker=[bfd|gold]
Date: Tue, 05 Jan 2010 23:00:00 -0000	[thread overview]
Message-ID: <20100105225955.1126A1F0@magilla.sf.frob.com> (raw)
In-Reply-To: Ian Lance Taylor's message of  Tuesday, 5 January 2010 13:35:08 -0800 <mcrfx6kdylv.fsf@dhcp-172-17-9-151.mtv.corp.google.com>

> Mainly because an alternative is to install them in subdirectories
> with the name ld.  Then gcc can run them directly using a -B option.
> I don't know which approach is best.

I think it keeps things simplest for humans to understand if the actual
binaries are available as ld.bfd and ld.gold.  If you then want some
obscure directory names containing an "ld" for gcc's use, then make those
symlinks.  Personally, I think -Wl,--gold (via $(bindir)/ld being a wrapper
script) is nicer than -B/usr/libexec/binutils/gold/ or whatnot.


Thanks,
Roland

  parent reply	other threads:[~2010-01-05 23:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 22:06 H.J. Lu
2009-11-03 22:19 ` H.J. Lu
2009-11-03 22:23   ` Roland McGrath
2009-11-03 23:28     ` H.J. Lu
2009-11-04  5:09       ` Roland McGrath
2009-11-04 14:47         ` H.J. Lu
2010-01-05 19:08       ` Ian Lance Taylor
2010-01-05 21:12         ` Roland McGrath
2010-01-05 21:35           ` Ian Lance Taylor
2010-01-05 21:40             ` H.J. Lu
2010-01-05 22:29               ` Ian Lance Taylor
2010-01-05 23:48                 ` Matthias Klose
2010-01-05 23:00             ` Roland McGrath [this message]
2010-01-05 23:52               ` Matthias Klose
2010-01-06  1:01                 ` Roland McGrath
2010-01-06  1:42                   ` Daniel Jacobowitz
2010-01-06 21:49                     ` Roland McGrath
2010-01-06  0:24               ` Ian Lance Taylor
2010-01-06  4:23         ` H.J. Lu
2010-01-12 15:27           ` 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=20100105225955.1126A1F0@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=iant@google.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).