From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25882@debbugs.gnu.org
Subject: bug#25882: gcc-wrapper doesn't handle response files
Date: Wed, 08 Mar 2017 13:57:10 +0100 [thread overview]
Message-ID: <878togudsp.fsf@lupo.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87r329fjcq.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 07 Mar 2017 11:53:57 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> On closer inspection, it’s an easy change to make.
>
> Could you test the attached patch with GHC?
Thanks for the patch. I've tested it with GHC 8.0.2 and seems to work
for it. However, this is an excerpt of the description of the use of
response files from the GCC manual:
--8<---------------cut here---------------start------------->8---
'@FILE'
Read command-line options from FILE. The options read are inserted
in place of the original @FILE option. If FILE does not exist, or
cannot be read, then the option will be treated literally, and not
removed.
Options in FILE are separated by whitespace. A whitespace
character may be included in an option by surrounding the entire
option in either single or double quotes. Any character (including
a backslash) may be included by prefixing the character to be
included with a backslash. The FILE may itself contain additional
@FILE options; any such options will be processed recursively.
--8<---------------cut here---------------end--------------->8---
The patch doesn't seems to handle several things, such as missing files,
recursion and use of quotes. I would suggest to try to match the
expected behavior in its entirety (or at least a larger part thereof).
Fede
next prev parent reply other threads:[~2017-03-08 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 16:58 bug#25882: gcc-wrapper doesn't handle response files Federico Beffa
2017-03-06 16:22 ` Ludovic Courtès
2017-03-06 17:16 ` Federico Beffa
2017-03-07 10:53 ` Ludovic Courtès
2017-03-08 12:57 ` Federico Beffa [this message]
2017-03-11 13:47 ` Ludovic Courtès
2017-03-12 11:36 ` Federico Beffa
2017-05-25 12:42 ` Ludovic Courtès
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=878togudsp.fsf@lupo.i-did-not-set--mail-host-address--so-tickle-me \
--to=beffa@ieee.org \
--cc=25882@debbugs.gnu.org \
--cc=ludo@gnu.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.
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.