summaryrefslogtreecommitdiff
path: root/m4
Commit message (Collapse)AuthorAge
* core: remove tcpwrap supportLennart Poettering2014-03-24
| | | | | | | | | | | | tcpwrap is legacy code, that is barely maintained upstream. It's APIs are awful, and the feature set it exposes (such as DNS and IDENT access control) questionnable. We should not support this natively in systemd. Hence, let's remove the code. If people want to continue making use of this, they can do so by plugging in "tcpd" for the processes they start. With that scheme things are as well or badly supported as they were from traditional inetd, hence no functionality is really lost.
* build: check for build/link flags harderDavid Herrmann2013-09-16
| | | | | | | | Use AC_LINK_IFELSE instead of AC_COMPILE_IFELSE to test for flags that might succeed during compilation but not during linking. An example is gcc compiled with libssp support but gnu-ld without it. In this case -fstack-protector works fine during compilation but fails during linking as several internal helpers are missing.
* replace tabs with spaces in various filesJason St. John2013-07-02
| | | | | | | | The affected files in this patch had inconsistent use of tabs vs. spaces for indentation, and this patch eliminates the stray tabs. Also, the opening brace of sigchld_hdl() in activate.c was moved so the opening braces are consistent throughout the file.
* Replace autoconf int max test with simple defineZbigniew Jędrzejewski-Szmek2013-01-22
|
* build-sys: add autoconf macro to pick macro for x32 compatibilityZbigniew Jędrzejewski-Szmek2013-01-18
|
* build-sys: Append -Werror when testing flagsLucas De Marchi2012-09-14
| | | | | | | | | | | | | | 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.
* move imported udev into placeKay Sievers2012-04-04
|
* build-sys: do not set CFLAGS directlyLucas De Marchi2012-03-26
| | | | | | | 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
* git: hide more files from gitLennart Poettering2011-07-14
|
* build-sys: fix AC_COMPILE_IFELSE testsLucas De Marchi2011-02-08
| | | | | | | | | | | | | | | | | | | | 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> ])], ...)
* git: ignore libtool m4 filesLennart Poettering2010-06-18
|
* socket: add optional libwrap supportLennart Poettering2010-06-16
|
* build: basic autoconfizationLennart Poettering2010-02-03