From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb-patches@sourceware.org
Subject: [RFA] Turn on -Werror by default
Date: Sun, 08 Jan 2006 17:59:00 -0000 [thread overview]
Message-ID: <200601081759.k08HxOxP007121@elgar.sibelius.xs4all.nl> (raw)
A while ago, we basically agreed that this would be a good thing to do
after the release. I tried to steal the code form BFD, but that
didn't really fit in very well in our configure.ac. Anyway, this adds
--enable-werror, defaulting to "yes", so to turn it off you'll
probably want to use --disable-werror. This is similar to what BFD
does, so you can easily disable -Werror for the whole tree. To
disable -Werror for GDB only, you can use
--enable-gdb-build-warnings=,-Wno-error.
ok?
Mark
Index: configure.ac
===================================================================
RCS file: /cvs/src/src/gdb/configure.ac,v
retrieving revision 1.25
diff -u -p -r1.25 configure.ac
--- configure.ac 17 Dec 2005 22:33:59 -0000 1.25
+++ configure.ac 8 Jan 2006 17:54:43 -0000
@@ -1109,6 +1109,24 @@ AC_ARG_WITH(sysroot,
AC_SUBST(TARGET_SYSTEM_ROOT)
AC_SUBST(TARGET_SYSTEM_ROOT_DEFINE)
+AC_ARG_ENABLE(werror,
+ [ --enable-werror treat compile warnings as errors],
+ [case "${enableval}" in
+ yes | y) ERROR_ON_WARNING="yes" ;;
+ no | n) ERROR_ON_WARNING="no" ;;
+ *) AC_MSG_ERROR(bad value ${enableval} for --enable-werror) ;;
+ esac])
+
+# Enable -Werror by default when using gcc
+if test "${GCC}" = yes -a -z "${ERROR_ON_WARNING}" ; then
+ ERROR_ON_WARNING=yes
+fi
+
+WERROR_CFLAGS=""
+if test "${ERROR_ON_WARNING}" = yes ; then
+ WERROR_CFLAGS="-Werror"
+fi
+
# NOTE: Don't add -Wall or -Wunused, they both include
# -Wunused-parameter which reports bogus warnings.
# NOTE: If you add to this list, remember to update
@@ -1164,7 +1182,6 @@ if test x"$silent" != x"yes" && test x"$
echo "Setting GDB specific compiler warning flags = $build_warnings" 6>&1
fi])dnl
WARN_CFLAGS=""
-WERROR_CFLAGS=""
if test "x${build_warnings}" != x -a "x$GCC" = xyes
then
AC_MSG_CHECKING(compiler warning flags)
next reply other threads:[~2006-01-08 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 17:59 Mark Kettenis [this message]
2006-01-08 22:25 ` Daniel Jacobowitz
2006-01-08 22:53 ` Mark Kettenis
2006-01-15 17:01 ` Daniel Jacobowitz
2006-01-15 17:56 ` Mark Kettenis
2006-01-15 18:21 ` Daniel Jacobowitz
2006-01-15 20:04 ` Mark Kettenis
2006-01-15 20:26 ` Daniel Jacobowitz
2006-01-15 20:40 ` Mark Kettenis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601081759.k08HxOxP007121@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.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