summaryrefslogtreecommitdiffstats
path: root/configure.ac (follow)
Commit message (Collapse)AuthorAgeFilesLines
* build-sys: allow building man pages even if disabled in ./configureZbigniew Jędrzejewski-Szmek2016-01-181-1/+1
| | | | | | | | | | | | | | This is purely for developer convenience: building man pages is slow so people tend to disable them when not working on documentation. But sometimes it is useful to build the man page to look something up, especially when working on an older machine which has outdated documentation, or to test some change to documentation. The rules to build man pages are now outside of the ENABLE_MANPAGES conditional, but they are not used unless manually invoked, and only the inclusion of man pages in build and install targets is affected by the conditional. Also, more generated files are removed in clean, which seems to be good thing, and Makefile.am is simplified.
* build-sys: refactor `have_smack` detectionEvgeny Vereshchagin2015-12-121-6/+3
|
* build-sys: fix ./configure --enable-smackEvgeny Vereshchagin2015-12-121-1/+1
| | | | | | | | | | | | | | Fixes: $ ./configure ... --enable-smack $ make src/core/load-fragment-gperf.c $ grep -i smack src/core/load-fragment-gperf.c {"Swap.SmackProcessLabel", config_parse_warn_compat, DISABLED_CONFIGURATION, 0}, ... should be {"Swap.SmackProcessLabel", config_parse_exec_smack_process_label, 0, offsetof(Swap, exec_context)}, ...
* importd: drop dkr supportLennart Poettering2015-12-101-9/+0
| | | | | | | | The current code is not compatible with current dkr protocols anyway, and dkr has a different focus ("microservices") than nspawn anyway ("whole machine containers"), hence drop support for it, we cannot reasonably keep this up to date, and it creates the impression we'd actually care for the microservices usecase.
* Merge pull request #2129 from poettering/dnssec3Tom Gundersen2015-12-101-4/+14
|\ | | | | Third DNSSEC patch series
| * build-sys: libgcrypt error messages make no sense without libgpg-errorLennart Poettering2015-12-101-4/+14
| | | | | | | | Hence, pull in this library too, if we need libgcrypt.
* | build: fix systemd-journal-upload installationEvgeny Vereshchagin2015-12-091-13/+22
|/ | | | | | | | | | | | Fixes: $ ./configure ... --disable-microhttpd --enable-libcurl --enable-sysusers $ make && make install DESTDIR=$(pwd)/INST $ ls INST/usr/lib/sysusers.d/ basic.conf systemd.conf There is no a file with `systemd-journald-upload`
* build: bump version numbersv228David Herrmann2015-11-181-1/+1
| | | | Prepare for v228 release and bump version numbers.
* build-sys: temporarily lower libmount version checkMartin Pitt2015-11-031-1/+1
| | | | | | | util-linux 2.27.1's configure.ac still claims to be 2.27.0, which breaks our version check. Lower it back to 2.27.0 until util-linux gets a fixed tarball. See #1754
* core: drop check for /etc/mtabMartin Pitt2015-11-021-1/+1
| | | | | | | | | | util-linux 2.27.1 now entirely stops looking at /etc/mtab, so we don't need to verify /etc/mtab during early boot any more. Later on, tmpfiles.d/etc.conf will fix /etc/mtab anyway, so there's not even a point in warning about it. Drop test_mtab() and bump the util-linux dependency to >= 2.17.1. Fixes #1495
* Merge pull request #1527 from keszybz/lz4Lennart Poettering2015-10-151-20/+26
|\ | | | | Using lz4 frame api for coredump files
| * build-sys: enable lz4 by default if availableZbigniew Jędrzejewski-Szmek2015-10-151-19/+25
| | | | | | | | | | | | | | | | --enable-lz4 can be used to force lz4 requirement, --disable-lz4 can be used to skip lz4 support even if available. Also, make surrounding checks for bzip2, xz, and zlib similar in structure. This fixes the check for requested but missing bzip2.
| * build-sys: use pkgconfig and lz4 and bump versionZbigniew Jędrzejewski-Szmek2015-10-111-2/+2
| | | | | | | | The new frame api was released in v. 125.
* | build: libdl is needed only for libnss_resolveMichal Schmidt2015-10-141-3/+4
| | | | | | | | | | Not everything needs to link to libdl. dlopen+dlsym are used only by libnss_resolve.
* | build: don't link everything to libcapMichal Schmidt2015-10-141-0/+1
| | | | | | | | | | | | | | | | | | The intent of the assignments around the check for libcap was obviously to avoid polluting LIBS. To work properly, LIBS must be restored from the save_LIBS variable. The practical effect is small though, because pretty much everything links with libbasic, which links with CAP_LIBS.
* | build: fix overlinking to libdwMichal Schmidt2015-10-141-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | We have two AC_CHECK_LIB checks for libdw. The first one has an empty action-if-found, so it defaults to adding "-ldw" to LIBS. LIBS are applied to everything we build. But only systemd-coredump needs libdw. It already links to ELFUTILS_LIBS correctly in Makefile.am. Drop the first AC_CHECK_LIB check. The second check is sufficient. Q: Don't we already use "-Wl,--as-needed" to eliminate overlinking? A: We do, but it is effective only for executables, not for shared libraries. This is due to a libtool bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347650
* | build-sys: check for xsltproc when building manpagesZbigniew Jędrzejewski-Szmek2015-10-121-2/+6
| | | | | | | | | | | | | | Only check for xsltproc if it will be used. If not found, complain. https://github.com/systemd/systemd/issues/1521
* | configure.ac: bump version numberDaniel Mack2015-10-071-1/+1
| |
* | ask-password: add support for caching passwords in the kernel keyringLennart Poettering2015-10-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for caching harddisk passwords in the kernel keyring if it is available, thus supporting caching without Plymouth being around. This is also useful for hooking up "gdm-auto-login" with the collected boot-time harddisk password, in order to support gnome keyring passphrase unlocking via the HDD password, if it is the same. Any passwords added to the kernel keyring this way have a timeout of 2.5min at which time they are purged from the kernel.
* | missing.h : add bridge paramsSusant Sahani2015-10-051-0/+1
| |
* | 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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-04 01:55:37 +0100