From: Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de>
Subject: [Patch] Only use -Werror with gcc
Date: Tue, 17 Jun 2003 13:52:46 +0200 [thread overview]
Message-ID: <uw57k7kyl81.fsf@saturn.math.uni-magdeburg.de> (raw)
Guile from CVS HEAD does not build with non-gcc compilers because the
-Werror flag is passed to the compiler when GUILE_ERROR_ON_WARNING is
yes (the default).
Here is a patch.
(Does anybody test Guile with non-gcc compilers?)
--- configure.in.~1.220.~ Mon Jun 16 16:49:24 2003
+++ configure.in Tue Jun 17 13:39:37 2003
@@ -969,15 +969,6 @@
fi
AC_SUBST(GUILE_FOR_BUILD)
-# Do this here so we don't screw up any of the tests above that might
-# not be "warning free"
-
-if test "${GUILE_ERROR_ON_WARNING}" = yes
-then
- CFLAGS="${CFLAGS} -Werror"
- enable_compile_warnings=no
-fi
-
## If we're using GCC, ask for aggressive warnings.
case "$GCC" in
yes )
@@ -986,7 +977,15 @@
## less than exasperating.
## -Wpointer-arith was here too, but something changed in gcc/glibc
## and it became equally exasperating (gcc 2.95 and/or glibc 2.1.2).
- CFLAGS="$CFLAGS -Wall -Wmissing-prototypes" ;;
+ CFLAGS="$CFLAGS -Wall -Wmissing-prototypes"
+ # Do this here so we don't screw up any of the tests above that might
+ # not be "warning free"
+ if test "${GUILE_ERROR_ON_WARNING}" = yes
+ then
+ CFLAGS="${CFLAGS} -Werror"
+ enable_compile_warnings=no
+ fi
+ ;;
esac
## NOTE the code below sets LIBOBJS directly and so is now forbidden
--
Matthias Köppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-06-17 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 11:52 Matthias Koeppe [this message]
2003-06-19 20:09 ` [Patch] Only use -Werror with gcc Marius Vollmer
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=uw57k7kyl81.fsf@saturn.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.de \
/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).