On Wed, 18 Jan 2006, Philip Martin wrote:
> Daniel Rall <email@example.com> writes:
> > On Wed, 18 Jan 2006, Philip Martin wrote:
> >> Daniel Rall <firstname.lastname@example.org> writes:
> >> > * configure.in
> >> > (OVERRIDE_CFLAGS): Add new substitution used when the compiler (CC)
> >> > is gcc, tacking "-Wno-uninitialized" onto the end of the
> >> > compilation flags. This additional substitution is necessary
> >> > because GCC 4.0.1 takes argument ordering of such flags into
> >> > consideration, and the flags may need to be positioned after
> >> > EXTRA_CFLAGS to take affect.
> >> Why should -Wno-uninitialized override EXTRA_CFLAGS? I thought that
> >> EXTRA_CFLAGS was *intended* to override the other CFLAGS.
> > Because the command-line positioning of gcc's compilation flags
> > impacts their interpretation, '-Wall -Werror -Wno-uninitialized'
> > works, while '-Wno-uninitialized -Wall -Werror' fails (I assume
> > because -Wall clobbers -Wno-uninitialized).
> I know that, but I don't see why that means -Wno-uninitialized in the
> Makefile has to override EXTRA_CFLAGS. EXTRA_CFLAGS is the way a user
> can override whatever is in the Makefile, you are making it impossible
> to override -Wno-uninitialized.
If EXTRA_CFLAGS includes -Wall, any -Wno-uninitialized flag added to
CFLAGS will be ignored by GCC, and result in compilation warnings.
This is especially annoying if EXTRA_CFLAGS includes -Werror, which
turns those warnings into build failures.
Given that Subversion's source code, when compiled using some version
of GCC, will always generate seemingly spurious warnings, it didn't
seem unreasonable to supress those warnings (regardless of
> If configure is going to put both -Wall and -Wno-uninitialized in the
> Makefile then it needs to ensure that they are in the right order, but
> they should both go before EXTRA_CFLAGS.
I didn't realize that CFLAGS already contained -Wall. It's not
explicitly added by our configure process, but I see it in Makefile.
Perhaps it's inherited from httpd or APR.
Using CFLAGS instead of an override which always turns off that type
of warning is easy enough (see below), but it seemed less appropriate
given the situation (since people can still easily shoot themself in
the foot). What do you think?
Disable GCC 4.0.1's inconsistent "uninitialized" warnings, which
otherwise cause build failures when using its '-Wall -Werror' flags.
A follow-up to the r18040/r18161 commit/revert.
(CFLAGS): Add new -Wno-uninitialized compilation flag onto the end
of this argument list when the compiler (CC) is gcc.
Suggested by: philip
--- configure.in (revision 18163)
+++ configure.in (working copy)
@@ -694,6 +694,16 @@
# ==== Miscellaneous bits ====================================================
+if test "$CC" = "gcc" ; then
+ # Turn off compilation warning known to cause problems with
+ # Subversion's source and GCC 4.0.1.
+ if echo "$CFLAGS" | grep '\-Wall' > /dev/null; then
+ if echo "$CFLAGS" | grep -v '\-Wno-uninitialized' > /dev/null; then
+ CFLAGS="$CFLAGS -Wno-uninitialized"
dnl Since this is used only on Unix-y systems, define the path separator as '/'
[Defined to be the path separator used on your local filesystem])
Received on Thu Jan 19 02:55:08 2006
- application/pgp-signature attachment: stored