From: Bruno Haible <bruno@clisp.org>
To: bug-guile@gnu.org
Subject: GUILE_CFLAGS contains warning options
Date: Sat, 19 Feb 2011 15:07:49 +0100 [thread overview]
Message-ID: <201102191507.50333.bruno@clisp.org> (raw)
Hi,
After guile-2.0.0 is installed using gcc, the installed file
$LIBDIR/pkgconfig/guile-2.0.pc contains a line such as
Cflags: -I${pkgincludedir}/2.0 -Wall -I$LIBUNISTRING_PREFIX/include -pthread -I$GC_PREFIX/include
and "guile-config compile" (which is used to define GUILE_CFLAGS through the
macro GUILE_FLAGS in $PREFIX/share/aclocal/guile.m4) produces output such as:
-Wall -pthread -I$PREFIX/include/guile/2.0 -I$LIBUNISTRING_PREFIX/include -I$GC_PREFIX/include
The presence of -Wall is IMO wrong for two reasons:
1) If I were to use a compiler different from gcc for compiling programs
that use guile (such as the vendor cc on Solaris, HP-UX, OSF/1, or AIX), it
would lead to an error when invoking that compiler.
2) Even if I use gcc, it's not guile's business to enable warning options on
_my_ code just because my code uses guile.
Bruno
--
In memoriam Friedrich Weißler <http://en.wikipedia.org/wiki/Friedrich_Weißler>
next reply other threads:[~2011-02-19 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 14:07 Bruno Haible [this message]
2011-02-19 17:17 ` GUILE_CFLAGS contains warning options 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
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=201102191507.50333.bruno@clisp.org \
--to=bruno@clisp.org \
--cc=bug-guile@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).