From: ludo@gnu.org (Ludovic Courtès)
To: 25803@debbugs.gnu.org
Subject: bug#25803: guile-snarf now fails when passed arguments contains whitespace
Date: Fri, 21 Apr 2017 17:00:54 +0200 [thread overview]
Message-ID: <87d1c524bd.fsf@gnu.org> (raw)
In-Reply-To: <20170219223639.61a78924@sf>
Hello,
Commit f775ab3654357fcaad294b95efb0b1c16de1eda8 (“guile-snarf: skip -g*
arguments to avoid build failure”) broke guile-snarf when passed
arguments with whitespace, as in:
guile-snarf -o auth.x auth.c -DPACKAGE_STRING=\"Guile-SSH\ 0.10.2\" …
The breakage comes from the fact that arguments are accumulated in a
string, in the ‘cpp_args’ variable, so the shell loses information about
word separation.
Besides, filtering out ‘-g’ arguments seems dubious.
WDYT?
Ludo’.
prev parent reply other threads:[~2017-04-21 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 22:36 bug#25803: ./configure CFLAGS=-ggdb3 fails 'guile-snarf' Sergei Trofimovich
2017-02-19 22:58 ` bug#25803: [PATCH] guile-snarf: skip -g* arguments to avoid build failure Sergei Trofimovich
2017-04-19 15:20 ` Andy Wingo
2017-04-21 15:00 ` Ludovic Courtès [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1c524bd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25803@debbugs.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.
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).