unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-guile@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: GUILE_CFLAGS contains warning options
Date: Sun, 20 Feb 2011 22:28:25 +0100	[thread overview]
Message-ID: <m3bp26z98m.fsf@unquote.localdomain> (raw)
In-Reply-To: <201102191507.50333.bruno@clisp.org> (Bruno Haible's message of "Sat, 19 Feb 2011 15:07:49 +0100")

On Sat 19 Feb 2011 15:07, Bruno Haible <bruno@clisp.org> writes:

> 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  

The template is:

  Cflags: -I${pkgincludedir}/@GUILE_EFFECTIVE_VERSION@ @GUILE_CFLAGS@ @BDW_GC_CFLAGS@

In my copy I have:

  Cflags: -I${pkgincludedir}/2.0  -pthread  

And in configure.ac I have:

  GUILE_CFLAGS="$CPPFLAGS $PTHREAD_CFLAGS"

You said that you configured like this:

  ./configure --host=x86_64-pc-linux-gnu \
              --prefix=/arch/x86_64-linux/gnu-inst-guile/2.0.0 \
              --libdir=/arch/x86_64-linux/gnu-inst-guile/2.0.0/lib64 \
              CPPFLAGS=-Wall \
              --with-libunistring-prefix=/arch/x86_64-linux/gnu-inst-libunistring/0.9.3

So it is the CPPFLAGS making it there.

I would just remove CPPFLAGS entirely, but it seems to be used to
communicate libunistring compilation flags to other parts of the build.
Ludo do you have any thoughts on this?

Thanks for the report,

Andy
-- 
http://wingolog.org/



  parent reply	other threads:[~2011-02-20 21: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 [this message]
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=m3bp26z98m.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=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).