summaryrefslogtreecommitdiff
path: root/m4
AgeCommit message (Collapse)Author
2012-09-14build-sys: Append -Werror when testing flagsLucas De Marchi
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-04-04move imported udev into placeKay Sievers
2012-03-26build-sys: do not set CFLAGS directlyLucas De Marchi
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
2011-07-14git: hide more files from gitLennart Poettering
2011-02-08build-sys: fix AC_COMPILE_IFELSE testsLucas De Marchi
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> ])], ...)
2010-06-18git: ignore libtool m4 filesLennart Poettering
2010-06-16socket: add optional libwrap supportLennart Poettering
2010-02-03build: basic autoconfizationLennart Poettering