4 Commits

Author	SHA1	Message	Date
Lucas De Marchi	cdefbd6aeb	build-sys: Append -Werror when testing flags ... 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.	2012-09-14 19:06:50 +02:00
Lucas De Marchi	eb2e280f9c	build-sys: do not set CFLAGS directly ... 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	2012-03-26 21:02:26 +02:00
Lucas De Marchi	c18514440d	build-sys: fix AC_COMPILE_IFELSE tests ... 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> ])], ...)	2011-02-08 12:11:53 +01:00
Lennart Poettering	47be870bd8	build: basic autoconfization	2010-02-03 14:21:48 +01:00