From: Kevin Ryde <user42@zip.com.au>
Subject: Re: guile-core does not build with gcc-2.95.4
Date: Mon, 14 Jul 2003 08:39:59 +1000 [thread overview]
Message-ID: <874r1q2gqo.fsf@zip.com.au> (raw)
In-Reply-To: <16145.56324.217251.910553@localhost.localdomain> (Han-Wen Nienhuys's message of "Mon, 14 Jul 2003 00:24:04 +0200")
Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
>
> Maybe --std=gnu89 should be added by default for GCC 3.x
> compilation. Anyone knowledgeable about autoconf willing to do this?
Personally I think it's cleaner to keep such things out of the main
configure.in (I think that of -Werror for instance too). Developers
can add such stuff easily enough.
I like CPPFLAGS for extra flags. CFLAGS is the right place, but one
can leave that to configure to establish, and instead insinuate extra
stuff by abusing CPPFLAGS.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-07-13 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 20:39 guile-core does not build with gcc-2.95.4 Alex Thiel
2003-07-09 22:03 ` Kevin Ryde
2003-07-13 15:36 ` Andreas Rottmann
2003-07-13 22:24 ` Han-Wen Nienhuys
2003-07-13 22:39 ` Kevin Ryde [this message]
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=874r1q2gqo.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).