From: ludo@gnu.org (Ludovic Courtès)
To: Bruno Haible <bruno@clisp.org>
Cc: bug-guile@gnu.org
Subject: Re: GUILE_CFLAGS contains warning options
Date: Sun, 27 Feb 2011 17:54:40 +0100 [thread overview]
Message-ID: <871v2tct9r.fsf@gnu.org> (raw)
In-Reply-To: <201102231128.54229.bruno@clisp.org> (Bruno Haible's message of "Wed, 23 Feb 2011 11:28:52 +0100")
[-- Attachment #1: Type: text/plain, Size: 44 bytes --]
Hello!
I’ll commit the patch below:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 744 bytes --]
diff --git a/configure.ac b/configure.ac
index 423ae99..9b8553f 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1566,9 +1566,18 @@ AC_SUBST(LIBGUILE_I18N_INTERFACE)
#######################################################################
-dnl Tell guile-config what flags guile users should compile and link with.
+dnl Tell guile-config what flags guile users should compile and link
+dnl with, keeping only `-I' flags from $CPPFLAGS.
GUILE_LIBS="$LDFLAGS $LIBS"
-GUILE_CFLAGS="$CPPFLAGS $PTHREAD_CFLAGS"
+GUILE_CFLAGS=""
+for flag in "$CPPFLAGS"
+do
+ case "$flag" in
+ -I*) GUILE_CFLAGS="$GUILE_CFLAGS $flag";;
+ *) ;;
+ esac
+done
+GUILE_CFLAGS="$GUILE_CFLAGS $PTHREAD_CFLAGS"
AC_SUBST(GUILE_LIBS)
AC_SUBST(GUILE_CFLAGS)
[-- Attachment #3: Type: text/plain, Size: 21 bytes --]
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-02-27 16:54 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
2011-02-27 16:54 ` Ludovic Courtès [this message]
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=871v2tct9r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=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).