From: Bruno Haible <bruno@clisp.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guile@gnu.org
Subject: Re: GUILE_CFLAGS contains warning options
Date: Wed, 23 Feb 2011 11:28:52 +0100 [thread overview]
Message-ID: <201102231128.54229.bruno@clisp.org> (raw)
In-Reply-To: <87hbbvawim.fsf@gnu.org>
Ludovic Courtès wrote:
> I only ever use CPPFLAGS for -I flags and can’t think of other likely
> uses.
If someone wants to disable assert()s, he uses the option -DNDEBUG, and
according to the autoconf manual [1]
"If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS"
this option belongs in CPPFLAGS.
But just because guile has been built with assertions turned off, doesn't
mean that every program that uses guile wants to disable assertions. So
this is a second reason to put only -I options from $CPPFLAGS into
guile-2.0.pc.
Bruno
[1] http://www.gnu.org/software/autoconf/manual/html_node/Preset-Output-Variables.html
--
In memoriam Henri Salmide <http://en.wikipedia.org/wiki/Henri_Salmide>
next prev parent reply other threads:[~2011-02-23 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 14:07 GUILE_CFLAGS contains warning options Bruno Haible
2011-02-19 17:17 ` Bruno Haible
2011-02-20 21:28 ` Andy Wingo
2011-02-20 22:50 ` Bruno Haible
2011-02-21 2:52 ` Ken Raeburn
2011-02-22 20:46 ` Ludovic Courtès
2011-02-22 21:40 ` Bruno Haible
2011-02-23 10:13 ` Ludovic Courtès
2011-02-23 10:28 ` Bruno Haible [this message]
2011-02-27 16:54 ` Ludovic Courtès
2011-02-27 21:59 ` Bruno Haible
2011-02-27 23:43 ` 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=201102231128.54229.bruno@clisp.org \
--to=bruno@clisp.org \
--cc=bug-guile@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.
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).