From: Daniel Jacobowitz <drow@false.org>
To: Richard Sandiford <rsandifo@redhat.com>
Cc: Mark Mitchell <mark@codesourcery.com>, binutils@sources.redhat.com
Subject: Re: PATCH: --sysroot-suffix
Date: Tue, 18 Jan 2005 16:06:00 -0000 [thread overview]
Message-ID: <20050118160622.GA12828@nevyn.them.org> (raw)
In-Reply-To: <wvnoefmlomr.fsf@talisman.cambridge.redhat.com>
On Tue, Jan 18, 2005 at 03:53:48PM +0000, Richard Sandiford wrote:
> OK, the concensus seemed to be that a --sysroot flag was worth having,
> and that it would be nice to support it on non-sysrooted linkers too,
> but that it wasn't necessary for the first cut.
>
> Here's a cleaned-up version of the patch, this time with docs and
> NEWS item. Tested on mips-linux-gnu. OK to install?
There seems to be plenty of precedent for --argument=value in GNU ld,
but the documentation says:
Arguments to multiple-letter options must either be
separated from the option name by an equals sign, or be given as
separate arguments immediately following the option that
requires them. For example, --trace-symbol foo and
--trace-symbol=foo are equivalent. Unique abbreviations of
the names of multiple-letter options are accepted.
I always use the space, personally, so I'd be pretty confused by the
dummy option handling; how about supporting that too?
I'm somewhat surprised the hack is necessary, but I'm sure you're right
:-)
As a first cut to fix the configury option, we could always enable
sysroots for native tools. Right now the differences in linker script
generation are only the addition of the '=' marker, the use of
NATIVE_LIB_DIRS (already enabled for natives), and something
complicated for $(tooldir) that I can't quite remember the purpose
of...
--
Daniel Jacobowitz
next prev parent reply other threads:[~2005-01-18 16:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 3:22 Mark Mitchell
2005-01-17 3:38 ` Daniel Jacobowitz
2005-01-17 4:04 ` Mark Mitchell
2005-01-17 10:54 ` Richard Sandiford
2005-01-17 11:37 ` Hans-Peter Nilsson
2005-01-17 11:44 ` Richard Sandiford
2005-01-17 14:33 ` Daniel Jacobowitz
2005-01-17 14:47 ` Richard Sandiford
2005-01-17 14:54 ` Daniel Jacobowitz
2005-01-17 16:33 ` Mark Mitchell
2005-01-18 15:54 ` Richard Sandiford
2005-01-18 16:06 ` Daniel Jacobowitz [this message]
2005-01-18 16:10 ` Richard Sandiford
2005-01-18 17:03 ` Daniel Jacobowitz
2005-01-18 17:07 ` Alexandre Oliva
2005-01-18 17:24 ` Mark Mitchell
2005-01-18 18:22 ` Richard Sandiford
2005-01-18 18:26 ` Mark Mitchell
2005-01-19 2:45 ` Alan Modra
2005-01-19 5:14 ` Mark Mitchell
2005-01-19 11:49 ` Richard Sandiford
2005-01-19 15:50 ` Mark Mitchell
2005-01-17 19:56 ` Hans-Peter Nilsson
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=20050118160622.GA12828@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=mark@codesourcery.com \
--cc=rsandifo@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).