unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
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: Tue, 22 Feb 2011 21:46:36 +0100	[thread overview]
Message-ID: <878vx7bxw3.fsf@gnu.org> (raw)
In-Reply-To: <201102202350.16563.bruno@clisp.org> (Bruno Haible's message of "Sun, 20 Feb 2011 23:50:15 +0100")

Hi Bruno,

Bruno Haible <bruno@clisp.org> writes:

> Andy Wingo wrote:
>> > $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@
>> ...
>> And in configure.ac I have:
>> 
>>   GUILE_CFLAGS="$CPPFLAGS $PTHREAD_CFLAGS"

[...]

> You can extract the -I options from $CPPFLAGS; this would be OK since all
> compilers support -I.

That’s probably the right thing to do.

However, why do you have -Wall in CPPFLAGS, instead of CFLAGS, in the
first place?  :-)

> For the PTHREAD_CFLAGS it is more tricky: On most platforms you can use
> "-lpthread" instead of "-pthread", and all compilers support -l options.
> But on OSF/1, the options for using threads are compiler dependent:
>   * -pthread for cc,
>   * -lpthread for gcc.

This and more, as Ken mentioned, so I’d leave it as is for now.

Thanks,
Ludo’.



  parent reply	other threads:[~2011-02-22 20:46 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 [this message]
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=878vx7bxw3.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).