From: Nicholas Clifton <nickc@redhat.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>,
binutils@sourceware.org
Subject: Re: RFC: allow a first "=" to mean sysroot for all paths in linker-scripts?
Date: Mon, 09 Jun 2014 13:56:00 -0000 [thread overview]
Message-ID: <5395BD06.2000403@redhat.com> (raw)
In-Reply-To: <201405270232.s4R2WUJL032457@ignucius.se.axis.com>
Hi Hans-Peter,
> Is there a reason not to allow a first character '=' to mean
> sysroot-prefix for all paths inside linker scripts?
No...
> So again, how about treating "=" as the sysroot prefix for
> *all* paths in linker scripts?
A good idea - please submit a patch.
> What to do about quoted paths?
> (I suggest both quoted and unquoted "="-prefixed paths to work.)
Hmm, I can think of no situation where a user would want to use = as a
valid first character of a real filepath, so quoted and unquoted
prefixes are fine.
Cheers
Nick
next prev parent reply other threads:[~2014-06-09 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 2:32 Hans-Peter Nilsson
2014-05-28 13:26 ` Hans-Peter Nilsson
2014-06-09 13:56 ` Nicholas Clifton [this message]
2014-10-09 2:55 ` [PATCH 0/6] Allow a first "=" to mean sysroot for all paths in linker-scripts 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=5395BD06.2000403@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=hans-peter.nilsson@axis.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).