From: Andy Wingo <wingo@igalia.com>
To: Sergei Trofimovich <slyfox@gentoo.org>
Cc: 25803-done@debbugs.gnu.org
Subject: bug#25803: [PATCH] guile-snarf: skip -g* arguments to avoid build failure
Date: Wed, 19 Apr 2017 17:20:27 +0200 [thread overview]
Message-ID: <871ssol8zo.fsf@igalia.com> (raw)
In-Reply-To: <20170219225840.5015-1-slyfox@gentoo.org> (Sergei Trofimovich's message of "Sun, 19 Feb 2017 22:58:40 +0000")
On Sun 19 Feb 2017 23:58, Sergei Trofimovich <slyfox@gentoo.org> writes:
> The fix is to ignore -g* flags. They should only affect debugging output.
>
> * libguile/guile-snarf.in: skip -g* arguments to avoid build failure
Applied. Thanks :)
Andy
next prev parent reply other threads:[~2017-04-19 15:20 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 [this message]
2017-04-21 15:00 ` bug#25803: guile-snarf now fails when passed arguments contains whitespace 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
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=871ssol8zo.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=25803-done@debbugs.gnu.org \
--cc=slyfox@gentoo.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).