summaryrefslogtreecommitdiff
path: root/m4/attributes.m4
Commit message (Collapse)AuthorAge
* build-sys: properly quote m4 macro arguments in CC_CHECK_FLAGS_APPENDFilipe Brandenburger2017-03-29
| | | | | | | | | | The variables should be quoted inside [...] to avoid double macro expansion. This is currently not an issue, since the values (-W...) are not really macros, but we might as well just fix that issue now. Tested by re-running autogen.sh and comparing the value of OUR_CFLAGS in the generated Makefile. Ran a full build from a clean tree to confirm no other issues were introduced.
* build: make sure to test for -Wflag instead of -Wno-flagDavid Herrmann2015-02-24
| | | | | | | | gcc does not support testing for negated warnings. See here for details: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63499 This patch changes CC_CHECK_FLAG_APPEND to always test for the non-negated warnings.
* s/commandline/command line/gHarald Hoyer2014-11-06
|
* build-sys: fix conftest.c to work on armZbigniew Jędrzejewski-Szmek2014-08-03
| | | | | | All tests for compiler support were failing with: /usr/bin/ld: /tmp/ccwnVc2A.o: relocation R_ARM_MOVW_ABS_NC against `a' can not be used when making a shared object; recompile with -fPIC
* 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.
* 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.
* 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
* 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> ])], ...)
* build: basic autoconfizationLennart Poettering2010-02-03