summaryrefslogtreecommitdiff
path: root/m4
Commit message (Collapse)AuthorAgeFilesLines
* build: compile with -Wno-duplicate-decl-specifierThomas Haller2016-03-091-0/+1
| | | | | | | Duplicated const specifiers are allowed by C99 and can easily happen in macros. Also, systemd's interal code will use them. Disable this warning, it doesn't seem useful.
* m4: update introspection.m4 with original file from gobject-introspectionThomas Haller2016-03-041-0/+2
| | | | | | | | Originally m4/introspection.m4 was copied from gobject-introspection repository. We however modified it in commit f6272144e98c00db18cf67. Reimport the file with latest changes, but still preserving our workaround.
* build: hack around compiler warning in g-ir-scannerThomas Haller2015-11-101-1/+1
| | | | | | | | | | | | | | | | | | | | The autoconf macro for GIR passes $CFLAGS to g-ir-scanner. g-ir-scanner extends those flags with the system-default which includes -D_FORTIFY_SOURCE=2. Probably it should not do that, but if you disable optimization, this results in a compler warning in "/usr/include/features.h" [1] export CFLAGS='-O0' # Happens both with clang or gcc. #export CC=clang git clean -fdx ./autogen.sh make Work around that by injecting -Wno-error to $CFLAGS when invoking g-ir-scanner. [1] Related: https://sourceware.org/bugzilla/show_bug.cgi?id=13979
* build: set -Werror when checking whether a -W<warning> option worksLubomir Rintel2015-09-291-1/+1
| | | | | | | | Otherwise the check is effectively a no-op and unknown options still get turned on. This results in unknown warnings when build without --with-extra-warnings=error: warning: unknown warning option '-Wno-unused-but-set-variable'; did you mean '-Wno-unused-const-variable'? [-Wunknown-warning-option]
* build: don't default to -Werrorlr/ancient-ubuntuLubomir Rintel2015-06-021-1/+1
| | | | | | | | | | It seems like a poor default for various downstream toolchains. We can't anticipate the compiler warnings for future compiler versions and older ones are prone to false positives. Also, older gdbus-codegen is known to generate code that triggers compiler warnings. Let's keep it enabled for maintainer builds and distcheck so that we're sure a tool chain that builds releases without warnings exists.
* build: correct help message about missing readline + termcap librariesDan Williams2015-05-111-1/+1
|
* build: fix clang + glib 2.43 buildLubomir Rintel2015-03-191-0/+3
| | | | Known glib issue. Fixes Fedora 22 build.
* build: disable warnings that trigger known clang problemsLubomir Rintel2015-03-191-16/+64
| | | | Fixes build with clang 3.5 on Fedora 21.
* build: disable warnings where macros expand to tautological comparisonsLubomir Rintel2015-03-191-1/+1
|
* build: fix detecting support for -Wno-* compiler flagsThomas Haller2015-02-241-1/+2
| | | | | | | | | | | Since GCC 4.4, gcc does not warn about unknown -Wno-* flags. At least, it does not warning unless another warning is raised as well (https://gcc.gnu.org/wiki/FAQ#wnowarning). We didn't notice up to now, because we only tested flags that GCC actually supports. Hack around this, by checking for the -W* counterpart instead.
* build: fix wrongly linking against libreadline in all applicationsThomas Haller2014-11-261-0/+2
| | | | | | | | | | Every Makefile in the subtrees would include -lreadline as part of LIBS, hence every application would link against the library. This was broken since we added 'm4/ax_lib_readline.m4'. Fixes: 29297f8531e24d4df616c5c3acace9e23a695a02
* dhcp: add systemd-based "internal" DHCP clientDan Williams2014-11-061-1/+1
| | | | | | | | | We must also remove -Waggregate-return from m4/compiler-warnings.m4 because systemd uses aggregate return (correctly) in a couple cases, and we cannot keep single-level makefiles and override aggregate-return only for the systemd sub-library. This client currently only supports DHCPv4 because the base systemd code does not yet fully support DHCPv6.
* build: renable -Wstrict-prototypes compiler warningThomas Haller2014-10-291-0/+1
| | | | | | | | | | | | | The warning -Wstrict-prototypes was disabled by commit db9b1df0e47996ff8aaea468a11e1e97f64ee126 . Enable it again, but avoid warnings for WiMax SDK by explicitly disabling the compiler warning where needed. Apparently clang does not produce a warning for -Wstrict-prototypes, hence we don't need a clang specific #pragma. Signed-off-by: Thomas Haller <thaller@redhat.com>
* build: refactor compiler_warnings.m4 macroThomas Haller2014-10-291-16/+12
| | | | | | | | | | | NM_COMPILER_WARNINGS still works the same, but rename variables to have a CFLAGS_* prefix. Also cleanup the construction of CFLAGS by appending to CFLAGS_MORE_WARNINGS variable instead of appending to CFLAGS, and resetting to SAVE_CFLAGS. Signed-off-by: Thomas Haller <thaller@redhat.com>
* build: ensure rl_echo_signal_char() exists in the readline libraryDan Williams2014-10-141-0/+13
|
* build/clang: fix detection of valid warning compiler flagsThomas Haller2014-08-011-1/+21
| | | | | | | | | | | | | | clang does not exit with error when it is called with an unrecognized (warning) option. Instead it just prints a warning that makes the configure script believe the warning is supported. Later, during build we might pass -Werror, which causes clang to fail due to unrecognized arguments. Fix the script to detect compiler warnings by passing '-Werror=unknown-warning-option', which lets clang fail too. Signed-off-by: Thomas Haller <thaller@redhat.com>
* build: check harder for readlineDan Williams2014-06-271-0/+106
| | | | | | | | | | | | Not all distros build their readline linked with a termcap library, since apps are (apparently) supposed to choose one for themselves and explicitly link to it when using readline. So add some checks to figure out whether readline is already linked, and if not, prefer ncurses since we use that for nmtui already. ax_lib_readline based off: http://www.gnu.org/software/autoconf-archive/ax_lib_readline.html
* build: add -Wformat-security to the default warning flagsDan Winship2014-04-021-1/+1
|
* build: update gnome-code-coverage.m4Dan Winship2013-05-091-5/+7
| | | | | | Update gnome-code-coverage.m4 from gnome-common to fix some (harmless) error messages when coverage is disabled (bug 699943), and to add support for lcov 1.10.
* coverage: delete *.gcno on make cleanPavel Šimerda2013-04-241-2/+2
|
* build: drop libnl 1.x and 2.x support, require libnl >= 3.2.7Pavel Šimerda2013-01-241-62/+0
|
* build: add code coverage supportPavel Šimerda2013-01-081-0/+162
| | | | | | | | Use the following in Makefile.am to enable code coverage for individual modules: @GNOME_CODE_COVERAGE_RULES@ my_program_LIBS = … $(CODE_COVERAGE_LDFLAGS) … my_program_CFLAGS = … $(CODE_COVERAGE_CFLAGS) …
* build: add some more build-time warningsDan Williams2012-07-301-1/+3
|
* vala: add vala bindings for libnm-util and libnm-glibAlberto Ruiz2012-06-121-0/+88
| | | | | | | This patch adds the autotools facilities to generate vapi files so that libnm-util and libnm-glib can be consumed from Vala. It depends on vapigen and it is a soft dependency.
* build: allow --set-more-warnings=no|yes|errorColin Walters2012-02-091-3/+5
| | | | | | | For the GNOME autobuilders, we want compiler warnings, but don't want -Werror. For developer compatibility, the default value is "error". https://bugzilla.gnome.org/show_bug.cgi?id=668974
* build: put test source code into AC_LANG_PROGRAM (bgo #655225)Krzesimir Nowak2011-07-281-7/+4
| | | | | This change silences autotools warnings about source code not being inside AC_LANG_SOURCE in AC_LANG_CONFTEST.
* build: don't use -Wstrict-prototypes (bgo #584947)Dan Williams2011-04-261-3/+4
| | | | | | | | First, -Wstrict-prototypes wasn't actually getting used because -Werror was already in CFLAGS and AC_TRY_COMPILE doesn't produce main() functions with valid strict prototypes. Suck. But even fixing that, the WiMAX SDK won't build with the flag, so just rip it out.
* build: use -Wundef and fix up cases where stuff wasn't defined (bgo #647157)Dan Williams2011-04-141-1/+2
|
* Merge remote branch 'origin/master' into rm-usersetDan Williams2011-01-251-1/+1
|\
| * build: turn off set-but-not-used variable warnings in new GCCDan Williams2011-01-241-1/+1
| |
* | introspection: add GObject introspection support (bgo #637032)Giovanni Campagna2011-01-211-0/+94
|/ | | | | | | Add the necessary annotations (the mininum required, that is those on return values. NULL parameters or container types may require more), and the Autotools stuff to get a NetworkManager GIR for libnm-util and a NMClient for libnm-glib.
* Work around libnl address caching bugDan Winship2009-08-261-0/+65
| | | | | | | | rtnl_addr requires that all addresses have the "peer" attribute set in order to be compared for equality, but this attribute is not normally set. As a result, most addresses will not compare as equal even to themselves, busting caching. We fix this for now by poking into the guts of libnl if it is broken...
* Split compiler warnings into separate m4 macro fileMichael Biebl2009-05-021-0/+31
The m4 macro is called NM_COMPILER_WARNINGS. Being in a separate file makes it easier reusable for the other NM projects.
View Lorry Controller Status