From: Nick Clifton <nickc@redhat.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: "H. J. Lu" <hjl@lucon.org>, binutils@sources.redhat.com
Subject: Re: housekeeping, -Wno-error
Date: Wed, 13 Apr 2005 15:35:00 -0000 [thread overview]
Message-ID: <425D3BC5.7050204@redhat.com> (raw)
In-Reply-To: <20050412114139.GF3321@bubble.modra.org>
Hi Alan,
> I've been playing with the following, along with Makefile.am changes
> to use $(NO_WERROR) in place of -Wno-error. The idea is to put this
> some place so that all the configure.in can use a common definition
> for warnings. I've changed it so that --enable-werror and
> --enable-build-warnings should be usable with compilers other than
> gcc.
>
> AC_DEFUN([AM_BINUTILS_WARNINGS],[
> WARN_CFLAGS="-W -Wall -Wstrict-prototypes -Wmissing-prototypes"
>
> 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
>
> NO_WERROR=
> if test "${ERROR_ON_WARNING}" = yes ; then
> WARN_CFLAGS="$WARN_CFLAGS -Werror"
> NO_WERROR="-Wno-error"
> fi
>
> AC_ARG_ENABLE(build-warnings,
> [ --enable-build-warnings Enable build-time compiler warnings],
> [case "${enableval}" in
> yes) ;;
> no) WARN_CFLAGS="-w";;
> ,*) t=`echo "${enableval}" | sed -e "s/,/ /g"`
> WARN_CFLAGS="${WARN_CFLAGS} ${t}";;
> *,) t=`echo "${enableval}" | sed -e "s/,/ /g"`
> WARN_CFLAGS="${t} ${WARN_CFLAGS}";;
> *) WARN_CFLAGS=`echo "${enableval}" | sed -e "s/,/ /g"`;;
> esac])
>
> if test x"$silent" != x"yes" && test x"$WARN_CFLAGS" != x""; then
> echo "Setting warning flags = $WARN_CFLAGS" 6>&1
> fi
>
> AC_SUBST(WARN_CFLAGS)
> AC_SUBST(NO_WERROR)
> ])
This seems like a very good approach. Would you consider applying it to
the relevant Makefile.am(s) please ?
Cheers
Nick
next prev parent reply other threads:[~2005-04-13 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 2:51 Alan Modra
2005-04-12 2:54 ` Daniel Jacobowitz
2005-04-12 4:36 ` H. J. Lu
2005-04-12 5:42 ` Alan Modra
2005-04-12 8:37 ` Nick Clifton
2005-04-12 11:41 ` Alan Modra
2005-04-13 15:35 ` Nick Clifton [this message]
2005-04-14 5:29 ` Alan Modra
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=425D3BC5.7050204@redhat.com \
--to=nickc@redhat.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.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).