From: Joseph Myers <joseph@codesourcery.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: <gcc-patches@gcc.gnu.org>,
<rb-general@lists.reproducible-builds.org>,
<anthraxx@archlinux.org>, <niels@thykier.net>
Subject: Re: [PATCH] gcc: read -fdebug-prefix-map OLD from environment (improved reproducibility)
Date: Thu, 10 Dec 2015 23:59:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1512102357320.14974@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1449768978-3872-1-git-send-email-dkg@fifthhorseman.net>
On Thu, 10 Dec 2015, Daniel Kahn Gillmor wrote:
> Specifically, if the first character of the "old" argument is a
> literal $, then gcc will treat it as an environment variable name, and
> use the value of the env var for prefix mapping.
I don't think a literal $ in option arguments is a good idea; it's far too
hard to pass through a sequence of shells and makefiles that you typically
get in recursive make. You end up with things like
'-Wl,-rpath,'\''\\\$$\$$\\\$$\$$ORIGIN'\''/../' (part of a process for
using $ORIGIN when linking GDB) if you try.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-12-10 23:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87egf1mxfl.fsf@alice.fifthhorseman.net>
2015-12-10 17:36 ` Daniel Kahn Gillmor
2015-12-10 22:05 ` Daniel Kahn Gillmor
2015-12-10 23:59 ` Joseph Myers [this message]
2015-12-11 0:13 ` Daniel Kahn Gillmor
2015-12-11 16:49 ` Daniel Kahn Gillmor
2015-12-11 17:03 ` Bernd Schmidt
2015-12-11 19:14 ` Daniel Kahn Gillmor
2015-12-15 12:19 ` Bernd Schmidt
2015-12-15 14:15 ` Daniel Kahn Gillmor
2015-12-15 16:08 ` Bernd Schmidt
2015-12-15 16:32 ` Daniel Kahn Gillmor
2015-12-22 12:16 ` [rb-general] " Thomas Klausner
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=alpine.DEB.2.10.1512102357320.14974@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=anthraxx@archlinux.org \
--cc=dkg@fifthhorseman.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=niels@thykier.net \
--cc=rb-general@lists.reproducible-builds.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).