From: ludo@gnu.org (Ludovic Courtès)
To: Shea Levy <shea@shealevy.com>
Cc: Guix-devel <guix-devel@gnu.org>,
gcc@gcc.gnu.org, nix-dev@lists.science.uu.nl,
cfe-dev@lists.llvm.org
Subject: Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment
Date: Tue, 18 Oct 2016 14:59:15 +0200 [thread overview]
Message-ID: <8737jtlsnw.fsf@gnu.org> (raw)
In-Reply-To: <87eg3d7vle.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me> (Shea Levy's message of "Tue, 18 Oct 2016 07:19:41 -0400")
Hi!
Shea Levy <shea@shealevy.com> skribis:
> Your patches look good! My biggest concern is how the ld wrapper behaves
> in the presence of response files. Have you tested that?
It surely doesn’t (yet?).
However, GCC does not pass “@file” arguments when it invokes ‘ld’, and
the bug report you mentioned¹ talks about GHC invoking ‘gcc’, not ‘ld’,
so I guess it’s fine to ignore response files in the ld wrapper.
Ludo’.
¹ https://github.com/NixOS/nixpkgs/commit/a421e7bd4a28c69bded8b17888325e31554f61a1
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
next prev parent reply other threads:[~2016-10-18 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r37gp8dt.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me>
2016-10-18 9:25 ` [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment Ludovic Courtès
[not found] ` <87vawqm2je.fsf-mXXj517/zsQ@public.gmane.org>
2016-10-18 11:03 ` Shea Levy via cfe-dev
2016-10-18 11:19 ` Shea Levy
2016-10-18 12:59 ` Ludovic Courtès [this message]
[not found] ` <8737jtlsnw.fsf-mXXj517/zsQ@public.gmane.org>
2016-10-18 13:46 ` Nathan Froyd via cfe-dev
[not found] ` <CAGepuV+VpTJfu=RUtEioxx47QgKDCvkeN40wisGt9aceXj1mDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-27 17:11 ` Will Dietz via cfe-dev
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=8737jtlsnw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cfe-dev@lists.llvm.org \
--cc=gcc@gcc.gnu.org \
--cc=guix-devel@gnu.org \
--cc=nix-dev@lists.science.uu.nl \
--cc=shea@shealevy.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.