summaryrefslogtreecommitdiffstats
path: root/configure.ac (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #1374 from olof/autoconf_gcrypt_depLennart Poettering2015-09-241-6/+15
|\ | | | | build-sys: only use AM_PATH_LIBGCRYPT macro if it exists
| * build-sys: only use AM_PATH_LIBGCRYPT macro if it existsOlof Johansson2015-09-241-6/+15
| | | | | | | | | | | | | | | | If gcrypt's m4 macro files aren't installed, with this change, gcrypt will be disabled --- unless gcrypt support was explicitly requested by passing --enable-gcrypt to configure, in which case it will fail. Without this change, autoconf would fail either way with not being able to resolve AM_PATH_LIBGCRYPT.
* | build: remove AC_FUNC_MALLOCJan Engelhardt2015-09-231-1/+0
| | | | | | | | | | | | | | | | | | What is the rationale to have AC_FUNC_MALLOC? It does not actually abort the configure run if an "unsuitable" malloc was found, and instead just replaces malloc by rpl_malloc, for which systemd however has no definition, either. Remove the call.
* | build-sys: Check behavior of -Werror=shadow before deciding to use itFilipe Brandenburger2015-09-221-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gcc versions 4.6 and earlier used to complain when a local variable shadows a global function, 4.7 and above only complain if a local variable shadows a global variable. Fix this by checking whether gcc 4.7+ behavior is in place before deciding to use -Werror=shadow in $(CFLAGS), by using a custom test program source that shadows a global function with a local variable and confirming that -Werror=shadow does not make the compile to break. Tested: - On gcc 4.7 and 4.8, confirmed nothing changed (other than the order of the -Werror=shadow argument, going to the end of CFLAGS.) - On gcc 4.6, confirmed by looking at the config.log output that the check for -Werror=shadow failed and it was not included in CFLAGS. - Ran `make V=1` to confirm -Werror=shadow was still in use, introduced a bogus shadowing issue and confirmed it was caught when building with a recent gcc.
* | mount: use libmount to monitor mountinfo & utabKarel Zak2015-09-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current implementation directly monitor /proc/self/mountinfo and /run/mount/utab files. It's really not optimal because utab file is private libmount stuff without any official guaranteed semantic. The libmount since v2.26 provides API to monitor mount kernel & userspace changes and since v2.27 the monitor is usable for non-root users too. This patch replaces the current implementation with libmount based solution. Signed-off-by: Karel Zak <kzak@redhat.com>
* | smack: label /etc/mtab as "_" when '--with-smack-run-label' is enabled.Sangjung Woo2015-09-101-1/+6
| | | | | | | | | | | | | | | | /etc/mtab should be labeled as "_", even though systemd has its own smack label using '--with-smack-run-label' configuration. This is mainly because all processes could read that file and the origin of this file (i.e. /proc/mounts) is labeled as "_". This labels /etc/mtab as "_" when '--with-smack-run-label' is enabled.
* | build: prepare for v226David Herrmann2015-09-081-1/+1
| | | | | | | | Bump version info and update NEWS for the upcoming release.
* | build-sys: remove sphinx binary from configure summaryMichael Biebl2015-09-061-1/+0
| | | | | | | | | | | | We no longer use sphinx as part of the build process so remove it from the configure summary as well. This is a leftover from commit 2799e519cabb6dfa99341b9a56ebd4dc2a4ec22a.
* | build-sys: Look for gcc-* binutils wrappers only if we're using GCCJan Alexander Steffens (heftig)2015-09-011-5/+8
| | | | | | | | | | | | | | If we don't look for them, LT_INIT will and default to the unprefixed tools. Apparently clang doesn't like the wrappers being used. Should fix #1077.
* | build-sys: bump versionsKay Sievers2015-08-261-1/+1
| |
* | build-sys: line-wrap message about google serversZbigniew Jędrzejewski-Szmek2015-08-071-1/+3
| | | | | | | | This way it is more readable in a wall of configure output.
* | build-sys: allow skipping installation of completionsZbigniew Jędrzejewski-Szmek2015-08-061-0/+2
| | | | | | | | | | | | | | ./configure --with-bashcompletiondir=no or --without-bashcompletiondir now works as expected. Similarly for zsh. https://github.com/systemd/systemd/issues/533
* | build: bump version to 224David Herrmann2015-07-311-1/+1
| | | | | | | | Prepare for bug-fix release and bump versions.
* | build-sys: use 'test -f' instead of AC_CHECK_FILEJohannes Nixdorf2015-07-311-2/+2
| | | | | | | | | | | | | | | | | | AC_CHECK_FILE fails when cross-compiling. It is intended to be used to check for files that are used at runtime during build time (e.g. /etc/passwd, /dev/*) [1]. For files which are only used at build time 'test -f' is sufficient. [1]: https://lists.gnu.org/archive/html/autoconf/2000-10/msg00018.html
* | build: bump version infov223David Herrmann2015-07-291-1/+1
| | | | | | | | | | Bump version to 223 and increase libsystemd libtool-info as we added a structure-member (without increasing structure size) to sd-bus-vtable.
* | terminal: drop unfinished codeDavid Herrmann2015-07-271-22/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This drops the libsystemd-terminal and systemd-consoled code for various reasons: * It's been sitting there unfinished for over a year now and won't get finished any time soon. * Since its initial creation, several parts need significant rework: The input handling should be replaced with the now commonly used libinput, the drm accessors should coordinate the handling of mode-object hotplugging (including split connectors) with other DRM users, and the internal library users should be converted to sd-device and friends. * There is still significant kernel work required before sd-console is really useful. This includes, but is not limited to, simpledrm and drmlog. * The authority daemon is needed before all this code can be used for real. And this will definitely take a lot more time to get done as no-one else is currently working on this, but me. * kdbus maintenance has taken up way more time than I thought and it has much higher priority. I don't see me spending much time on the terminal code in the near future. If anyone intends to hack on this, please feel free to contact me. I'll gladly help you out with any issues. Once kdbus and authorityd are finished (whenever that will be..) I'll definitely pick this up again. But until then, lets reduce compile times and maintenance efforts on this code and drop it for now.
* | Merge pull request #682 from ssahani/bridgeLennart Poettering2015-07-231-1/+1
|\ \ | | | | | | networkd: add bridge link properties
| * | Add bridge NL params to missing.hSusant Sahani2015-07-231-1/+1
| | |
* | | Merge pull request #604 from heftig/masterLennart Poettering2015-07-231-1/+6
|\ \ \ | |/ / |/| | build-sys: Use slim LTO objects if possible
| * | build-sys: Use slim LTO objects if possibleJan Alexander Steffens (heftig)2015-07-161-1/+6
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | While 235c6e6 gets LTO builds running again, it goes back to using fat LTO objects instead of using gcc-{ar,nm,ranlib}. Building these fat objects takes significantly more time. Use the suggested solution and look for gcc-{ar,nm,ranlib}, which launch the binutils tools with the appropriate --plugin parameter. GCC versions that do not ship these should either default to -ffat-lto-objects or do not support LTO at all. On another note, nm from binutils 2.25 seems to be smart enough to load the LTO plugin when needed without having to specify --plugin.
* | Tunnel NL params: Add to missing.hSusant Sahani2015-07-221-0/+1
| |
* | add NL parameters to missing.hSusant Sahani2015-07-201-1/+1
|/
* build-sys: warn if people don't change the default NTP servers when building ↵Lennart Poettering2015-07-111-1/+2
| | | | | | | | systemd Also, explain the situation in the docs. Relates to #437
* Merge pull request #501 from keszybz/remove-python-systemdDaniel Mack2015-07-081-28/+1
|\ | | | | Remove python-systemd
| * Remove python-systemdZbigniew Jędrzejewski-Szmek2015-07-071-28/+1
| | | | | | | | | | python-system has moved to it's own repository: https://github.com/systemd/python-systemd
* | Bump version to 222David Herrmann2015-07-071-1/+1
|/
* smack: add default smack process label configWaLyong Cho2015-06-221-2/+8
| | | | | | | | | | | | | | | | | Similar to SmackProcessLabel=, if this configuration is set, systemd executes processes with given SMACK label. If unit has SmackProcessLabel=, this config is overwritten. But, do NOT be confused with SMACK64EXEC of execute file. This default execute process label(and also label which is set by SmackProcessLabel=) is set fork-ed process SMACK subject label and used to access the execute file. If the execution file has also SMACK64EXEC, finally executed process has SMACK64EXEC subject. While if the execution file has no SMACK64EXEC, the executed process has label of this config(or label which is set by SmackProcessLabel=). Because if execution file has no SMACK64EXEC then excuted process inherits label from caller process(in this case, the caller is systemd).
* build-sys: bring back an intltool-update workaroundDaniel Mack2015-06-191-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, 'make distcheck' fails with an error such as this: srcdir=../../po /usr/bin/intltool-update -m The following files contain translations and are currently not in use. Please consider adding these to the POTFILES.in file, located in the po/ directory. build2/src/core/org.freedesktop.systemd1.policy.in build3/src/core/org.freedesktop.systemd1.policy.in [...] This is caused by a new behavior of autmake 1.15 which changed the location of the build tree during 'make distcheck', and the fact that intltool doesn't yet ignore that paths. We used to have a workaround in configure.ac that makes the failing call a no-op, but it was accidentially removed in 23756070 ("remove gudev and gtk-doc"). Bring back that snipet for now, until intltool and automake sorted out their issues and like each other again. Also see https://bugs.launchpad.net/intltool/+bug/1117944
* build-sys: bump versions and sonamesLennart Poettering2015-06-181-1/+1
|
* turn kdbus support into a runtime optionKay Sievers2015-06-171-3/+3
| | | | | | | | | | | | | ./configure --enable/disable-kdbus can be used to set the default behavior regarding kdbus. If no kdbus kernel support is available, dbus-dameon will be used. With --enable-kdbus, the kernel command line option "kdbus=0" can be used to disable kdbus. With --disable-kdbus, the kernel command line option "kdbus=1" is required to enable kdbus support.
* build-sys: Drop include_prefixMichael Biebl2015-06-141-1/+0
| | | | Appears to be unused and a leftover from the udev merge.
* build-sys: simplify lib dependenciesKay Sievers2015-06-141-6/+0
|
* build-sys: suppress warnings of unused resultsFilipe Brandenburger2015-06-111-0/+1
| | | | | | | | | | | | | | | | | | | | Unfortunately, gcc keeps warning about those even when we use an explicit (void) cast to indicate we are not interested in the result. LLVM's clang does not have that issue and works fine with the casts. GCC bug being tracked at: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425 Until that GCC bug is fixed (and the version with the fix is in many/most distributions) or we switch to LLVM as the default compiler, it looks like we'll have to disable this warning by default... Tested by building files known to present warnings about unused results without the suppression, confirmed that the warnings were no longer present with this patch applied. This partially reverts commit 00c11bc53a1d37 ("build-sys: don't suppress irrelevant warnings").
* build-sys: upgrade shadow variable warnings to errorsLennart Poettering2015-06-101-0/+1
|
* build-sys: turn some warnings into errorsDaniel Mack2015-06-101-2/+4
| | | | | | | | | Make the build sys error out on missing function prototypes, missing variable declarations, implicit function declarations or forgotten return statements. None of these conditions are acceptable, and by making them hard errors, the build bots can detect them earlier.
* build-sys: don't suppress irrelevant warningsThomas Hindoe Paaboel Andersen2015-06-081-4/+0
| | | | We do not trigger these warnings so no need to suppress them.
* Merge pull request #60 from Keruspe/masterDaniel Mack2015-06-031-1/+0
|\ | | | | build-sys: drop references to gobject-introspection
| * build-sys: drop references to gobject-introspectionMarc-Antoine Perennou2015-06-031-1/+0
| | | | | | | | It has been removed alongside gudev
* | Merge pull request #55 from filbranden/rootprefix_empty1Daniel Mack2015-06-031-0/+7
|\ \ | | | | | | Fix --with-rootprefix= (empty) with a workaround for now.
| * | build-sys: Work around --with-rootprefix= (empty) not producing /Filipe Brandenburger2015-06-031-0/+7
| |/ | | | | | | | | | | | | | | | | | | | | Since we introduced AX_NORMALIZE_PATH, using --with-rootprefix=/ does produce an empty string, but using --with-rootprefix= (empty) now produces "." instead which is wrong. Work around it until we can find a better solution for AX_NORMALIZE_PATH upstream at autoconf-archive. Bug: https://github.com/systemd/systemd/issues/54
* / build-sys: disable gc-sections if optimization is disabledKay Sievers2015-06-031-3/+12
|/ | | | | | This way, development builds will not rely on gc-sections to paper over cyclic link dependencies. Newly introduced broken link requirements will immediatley fail.
* configure.ac: add missing kommaKay Sievers2015-06-031-1/+1
|
* point to github issues instead of freedesktop bugzillaKay Sievers2015-06-031-1/+1
|
* remove gudev and gtk-docKay Sievers2015-06-031-38/+2
| | | | | The library moved to: https://git.gnome.org/browse/libgudev/
* build-sys: Normalize paths of configure optionsMichael Biebl2015-06-021-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | Strip trailing slashes from options such as --with-rootprefix, so that building with rootprefix="/" results in paths like "/lib" instead of "//lib". Also handle paths such as "/usr/" gracefully. Use m4/ax_normalize_path.m4 from the autoconf-archive project, which is now included in our tree as per usual practices in using autoconf-archive macros. Tested with the following configure options: ./configure \ --with-rootprefix=/ \ --with-rootlibdir=/lib64/ \ --prefix=/usr/ \ --libdir=/lib/ \ --with-bashcompletiondir=/bash-completion/completions/ (The "prefix" and "libdir" are already automatically normalized by Autoconf, this command is testing the others.) Compared the config.log and resulting trees (in particular man pages) to confirm double slashes were not present in the latter. Also tested that a configuration using default options is not affected and that `make distcheck` still works as expected.
* build-sys: pass originally configured --enable-split-usr to distcheckMartin Pitt2015-05-291-0/+1
| | | | | | | | | | Previously we always ran distcheck with --disable-split-usr. This caused test-path-util to fail with Assertion 'fsck_exists("minix") == 0' failed at ../src/test/test-path-util.c:224, function test_fsck_exists(). Aborting. as looking up fsck.minix would only look into DEFAULT_PATH_NORMAL, but on these systems fsck is in /sbin/.
* systemctl: drop hardcoded chkconfig invocationMartin Pitt2015-05-281-20/+0
| | | | | | | | | | | | | | Introduce /usr/lib/systemd/systemd-sysv-install [--root=] <action> <name> abstraction, replacing the direct calling of chkconfig. This allows distributions to call their specific tools like update-rc.d without patching systemd. Ship systemd-sysv-install.SKELETON as an example for packagers how to implement this. Drop the --enable-chkconfig configure option. Document this in README and point to it in NEWS.
* missing: add more IFLA_VXLAN_* definesMichael Olbrich2015-05-271-1/+1
| | | | Otherwise building faild with kernel headers < v3.16
* build-sys: bump library and package versionsLennart Poettering2015-05-211-1/+1
|
* Default to /usr/bin/u?mount, configurable, rather than hard-coded /bin/u?mount.Dimitri John Ledkov2015-05-131-0/+3
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-04 15:15:52 +0100