| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Clang don't treat unknown warnings flags as an error, but rather as a
warning. The result is that the detection for whic CFLAGS are supported
by this compiler will not work, since the compilation will succeed.
With this patch we now successfully detect clang doesn't support
-Wlogical-op, as opposed to previous behavior:
checking if clang supports flag -Wlogical-op in envvar CFLAGS... no
We use this macro only for LDFLAGS and CFLAGS, so it's safe to stash
-Werror there.
|
|
|
|
Set a separate variable for adding warning flags. Build systems are not
supposed to change CFLAGS and LDFLAGS, these are user variables.
Reference: http://www.gnu.org/software/automake/manual/html_node/Flag-Variables-Ordering.html
|
|
|
|
This removes some warnings when bootstrapping. The warnings were introduced
in autoconf 2.68. Reference:
http://www.flameeyes.eu/autotools-mythbuster/forwardporting/autoconf.html
The following code
AC_COMPILE_IFELSE([
<MY C CODE HERE>
], ...)
is changed to
AC_COMPILE_IFELSE(
[AC_COMPILE_IFELSE([AC_LANG_SOURCE([
<MY C CODE HERE>
])], ...)
|
|
|
|
|
|
|
