summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAge
* build-sys: add --disable-dbus autoconf optionZbigniew Jędrzejewski-Szmek2014-01-02
|
* Use format patterns for usec_t, pid_t, nsec_t, usec_tZbigniew Jędrzejewski-Szmek2014-01-02
| | | | | | | | It is nicer to predefine patterns using configure time check instead of using casts everywhere. Since we do not need to use any flags, include "%" in the format instead of excluding it like PRI* macros.
* build-sys: fix generation of user@.serviceZbigniew Jędrzejewski-Szmek2013-12-27
|
* build-sys: the pure/const warning options are probably too much as default, ↵Lennart Poettering2013-12-25
| | | | but let's make it available via "autogen.sh a"
* bus: rename message "serial" to "cookie"Lennart Poettering2013-12-25
| | | | | | Even if the lower-leveld dbus1 protocol calls it "serial", let's expose the word "cookie" for this instead, as this is what kdbus uses and since it doesn't imply monotonicity the same way "serial" does.
* build-sys: build bus-driverd if kdbus support is enabledLennart Poettering2013-12-17
|
* Add bus-driverdDaniel Mack2013-12-16
| | | | | | | | | | | | systemd-bus-driverd is a small daemon that connects to kdbus and implements the org.freedesktop.DBus interface. IOW, it provides the bus functions traditionally taken care for by dbus-daemon. Calls are proxied to kdbus, either via libsystemd-bus (were applicable) or with the open-coded use of ioctl(). Note that the implementation is not yet finished as the functions to add and remove matches and to start services by name are still missing.
* build-sys: warn if builds are not byte-by-byte reproducible due to usage of ↵Lennart Poettering2013-12-16
| | | | __DATE__ and suchlike
* build-sys: fix help text for --enable-kdbusLukasz Skalski2013-12-13
|
* bus: do kdbus only if this is enabled on the configure switchLennart Poettering2013-11-30
| | | | | | | | | | | | | | Since we want to retain the ability to break kernel ←→ userspace ABI after the next release, let's not make use by default of kdbus, so that people with future kernels will not suddenly break with current systemd versions. kdbus support is left in all builds but must now be explicitly requested at runtime (for example via setting $DBUS_SESSION_BUS). Via a configure switch the old behaviour can be restored. In fact, we change autogen.sh to do this, so that git builds (which run autogen.sh) get kdbus by default, but tarball builds (which ue the configure defaults) do not get it, and hence this stays out of the distros by default.
* Revert "build-sys: avoid warnings from assert_cc"Lennart Poettering2013-11-29
| | | | | | | This reverts commit f1a1264d13b31b9f5521f482d9a5a9d78da55efb. We can turn this off with a pragma only on old gcc. Newer gcc doesn't need this, so let's not turn this off for everybody.
* build-sys: use C99Zbigniew Jędrzejewski-Szmek2013-11-28
| | | | We already use various constructs, so let's just admit that we're using C99.
* build-sys: make multi-seat-x optionalZbigniew Jędrzejewski-Szmek2013-11-28
| | | | | | At some point it should become disabled by default. http://lists.freedesktop.org/archives/systemd-devel/2013-November/014869.html
* build-sys: avoid warnings from assert_ccZbigniew Jędrzejewski-Szmek2013-11-28
|
* build-sys: enable gcc Link Time Optimization when optimization is enabledKay Sievers2013-11-21
|
* valgrind: make running PID 1 in valgrind usefulLennart Poettering2013-11-20
| | | | | Since valgrind only generates useful output on exit() (rather than exec()) we need to explicitly exit when valgrind is detected.
* build: Allow disabling maintainer modeUmut Tezduyar Lindskog2013-11-14
| | | | | | | | | | | | | | | | | | | | This allows make rules for generated build files (i.e. configure, Makefile.in, ... ) to be skipped. This is useful when the source is stored without timestamps (for example in CVS or GIT). When the build rules trigger to regenerate the build files, it tries to use the same autotools version (currently 1.14) as was originally used for the release. Since many of our build machines run Debian Squeeze, they only have autotools 1.11 available and the build fails. Currently, we have to work around this by touching all the generated files before building to avoid triggering the make rule. With this patch, we would be able to just run configure with --disable-maintainer-mode instead. The patch sets the default to enable to not change the default behavior. Ref: http://git.kernel.org/cgit/utils/kernel/kmod/kmod.git/commit/ ?id=f5cc26c77d2f332a9b40f51f0ec72e95711edf1e
* build-sys: Add --disable-networkd optionColin Walters2013-11-12
| | | | | | | | | For GNOME (Continuous), we are unlikely to require or want systemd-networkd in the near term future; all of the tools and code are targeting NetworkManager. The long term story is still an open question of course, but for now, there's no reason for gnome-continuous to build or ship this.
* bus: test-bus-marshal - make dbus-1 optionalKay Sievers2013-11-06
|
* build-sys: disable _FORTIFY_SOURCE for -Og builds for nowKay Sievers2013-10-21
| | | | | | | | | | | | Older gcc versions throw things like: In file included from /usr/include/fcntl.h:302:0, from ../src/core/execute.c:25: In function 'open', inlined from 'open_null_as' at ../src/core/execute.c:196:12: /usr/include/bits/fcntl2.h:50:24: error: call to '__open_missing_mode' declared with attribute error: open with O_CREAT in second argument needs 3 arguments __open_missing_mode ();
* bus: remove static introspection file exportKay Sievers2013-10-21
|
* Fix kmod error message to have correct version requirementDavid Strauss2013-10-17
|
* static-nodes: don't call mkdirTom Gundersen2013-10-17
| | | | This is no longer necessary with kmod-15. Bump the requirement.
* rfkill: add new rfkill tool to save/restore rfkill state across rebootsLennart Poettering2013-10-14
| | | | This works analogous to the existing backlight and random seed services
* Run with a custom SMACK domain (label).Auke Kok2013-10-07
| | | | | | | | | | | Allows the systemd --system process to change its current SMACK label to a predefined custom label (usually "system") at boot time. This is needed to have a few system-generated folders and sockets automatically be created with the right SMACK label. Without that, processes either cannot communicate with systemd or systemd fails to perform some actions.
* build-ss: prepare new releaseLennart Poettering2013-10-02
|
* hashmap: randomize hash functions a bitLennart Poettering2013-10-01
|
* build-sys: don't fallback to upstart defaultsLennart Poettering2013-10-01
|
* build-sys: restore detection of sphinxZbigniew Jędrzejewski-Szmek2013-09-27
|
* build-sys: add ./configure --enable-address-sanitizerZbigniew Jędrzejewski-Szmek2013-09-26
| | | | | | | | | Enabling address sanitizer seems like a useful thing, but is quite tricky. Proper flags have to be passed to CPPFLAGS, CFLAGS and LDFLAGS, but passing them on the commandline doesn't work because we tests are done with ld directly, and not with libtool like in real linking. We might want to fix this, but let's add a handy way to enable address checking anyway.
* build-sys: don't build python modules after --without-pythonZbigniew Jędrzejewski-Szmek2013-09-19
| | | | | | | | | | The modules should build just fine, but AM_PATH_PYTHON sets pkgpyexecdir for us. Without that variable we don't know where to install modules. In addition libtool tries an empty rpath, breaking the build. Those issues could be fixed or worked around, but we probably don't have many people who want to avoid using python binary, but want to compile python modules. If such uses ever come up, this issue should be revisited.
* build-sys: prepare 207Lennart Poettering2013-09-13
|
* Add pam configuration to allow user sessions to work out of the boxZbigniew Jędrzejewski-Szmek2013-09-11
| | | | | | | | | | | | | | | | | | | systemd-logind will start user@.service. user@.service unit uses PAM with service name 'systemd-user' to perform account and session managment tasks. Previously, the name was 'systemd-shared', it is now changed to 'systemd-user'. Most PAM installations use one common setup for different callers. Based on a quick poll, distributions fall into two camps: those that have system-auth (Redhat, Fedora, CentOS, Arch, Gentoo, Mageia, Mandriva), and those that have common-auth (Debian, Ubuntu, OpenSUSE). Distributions that have system-auth have just one configuration file that contains auth, password, account, and session blocks, and distributions that have common-auth also have common-session, common-password, and common-account. It is thus impossible to use one configuration file which would work for everybody. systemd-user now refers to system-auth, because it seems that the approach with one file is more popular and also easier, so let's follow that.
* build-sys: Add configure check for linux/btrfs.hMichael Marineau2013-08-16
| | | | | | | | | | | btrfs.h was added to uapi in Linux 3.9. To fix building with older header versions this adds a configure check for the header and re-adds btrfs definitions to missing.h which was removed in bed2e820 along with two other ioctls used by gpt-auto-generator. [ Apparently, btrfs.h was only added recently: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=55e301fd57a6239ec14b91a1cf2e70b3dd135194 let's re-add it for now -- kay ]
* backlight: add minimal tool to save/restore screen brightness across rebootsLennart Poettering2013-08-14
| | | | | | | | | | As many laptops don't save/restore screen brightness across reboots, let's do this in systemd with a minimal tool, that restores the brightness as early as possible, and saves it as late as possible. This will cover consoles and graphical logins, but graphical desktops should do their own per-user stuff probably. This only touches firmware brightness controls for now.
* zsh_completion: fix zsh completion installationWilliam Giokas2013-08-02
| | | | | | | | | | Moved zsh shell completion to shell-completion/zsh/_systemd for automake's sake. Also allow users to specify where the files should go with:: ./configure --with-zshcompletiondir=/path/to/some/where and by default going to `$datadir/zsh/site-functions`
* build-sys: support old glibc versions without clock_gettime()Kay Sievers2013-07-30
|
* build: do not link everything with -lrt (and therefore -pthread)Shawn Landden2013-07-30
|
* build-sys: use pkg-config for python compilation flagsZbigniew Jędrzejewski-Szmek2013-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | Python 2.7, and 3.2 and higher support querying compilation flags through pkg-config. This makes python support follow rules similar to various other optional compilation-time libraries. New flags are called PYTHON_DEVEL_CFLAGS and PYTHON_DEVEL_LIBS, because PYTHON (without _DEVEL), is already used for the python binary name, and things would be confusing if the same prefix was used for two things. configure has --disable-python-devel to disable python modules. One advantage is that CFLAGS for modules gets smaller: - -I/usr/include/python3.3m -I/usr/include/python3.3m -Wno-unused-result -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv + -I/usr/include/python3.3m as does LIBS: - -lpthread -ldl -lutil -lm -lpython3.3m + -lpython3.3m Support for Python 2.6 is removed, but can be easily restored by using PYTHON_DEVEL_CFLAGS="$(python2.6-config --cflags)", etc., as ./configure parameters. https://bugs.freedesktop.org/show_bug.cgi?id=57800
* build-sys: prepare 206Lennart Poettering2013-07-23
|
* systemd-python: fix iterationZbigniew Jędrzejewski-Szmek2013-07-17
| | | | | Back in 6a58bf4135 raising stop iteration was removed from the C code, but wasn't added in the Python counterpart.
* switch from udev keymaps to hwdbKay Sievers2013-07-16
|
* build-sys: discover the path to kexec during build timeZbigniew Jędrzejewski-Szmek2013-07-15
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=55248
* cryptsetup: Add tcrypt supportJan Janssen2013-07-16
| | | | | | | | | | | | | | Tcrypt uses a different approach to passphrases/key files. The passphrase and all key files are incorporated into the "password" to open the volume. So, the idea of slots that provide a way to open the volume with different passphrases/key files that are independent from each other like with LUKS does not apply. Therefore, we use the key file from /etc/crypttab as the source for the passphrase. The actual key files that are combined with the passphrase into a password are provided as a new option in /etc/crypttab and can be given multiple times if more than one key file is used by a volume.
* Add test coverage and generate report with lcovThomas H.P. Andersen2013-07-13
| | | | | | | | | | | | | | Enable coverage with --enable-coverage. "make coverage" will create the report locally, "make coverage-sync" will upload the report to http://www.freedesktop.org/software/systemd/coverage/. Requires lcov version 1.10 to handle naming in systemd and to use the --no-external option. [zj: make the coverage at least generate something with separate build dir, simplify rules a bit: all errors are mine. ]
* Revert "build-sys: don't enable color gcc on dumb terminals"Zbigniew Jędrzejewski-Szmek2013-07-12
| | | | | | | | | This reverts commit cd3069559a09b4e4f85a6f02aa8f0521f48359ca. Emacs compilation can be fixed by putting (custom-set-variables '(compilation-environment (quote ("GCC_COLORS=")))) in ~/.emacs.
* build-sys: don't enable color gcc on dumb terminalsLennart Poettering2013-07-12
| | | | | | | | Guys, we know that emacs is the best editor on earth, but unfortunately its "M-x compile" terminal cannot do colors (well, it does its own highlighting of the output anyway), and it will inform the programs it calls about this with TERM=dumb, and gcc should check for that. But you guys turned that off. Not cool. Let's turn it on again.
* configure: split checks for libkmod >= 14Dave Reisner2013-07-11
| | | | | | | | | | PKG_CHECK_EXISTS won't created a cached variable that later messes with our PKG_CHECK_MODULES check for an explicit version. Unfortunately, nesting these checks as the code existed lead to an odd error. Rather, split the checks apart. This also improves to the error message when the requisite version isn't found, and supplies the literal version systemd needs.
* configure: fail if out-of-date kmod found and kmod not disabledTom Gundersen2013-07-09
| | | | | | | | Almost everyone wants kmod support, so don't fail silently if the libs are out-of-date. kmod can still be explicitly disabled and if it is not found at all, we still default to disabling it.
* static-nodes: move creation of static nodes from udevd to tmpfilesTom Gundersen2013-07-08
| | | | | | | | | | | | | As of kmod v14, it is possible to export the static node information from /lib/modules/`uname -r`/modules.devname in tmpfiles.d(5) format. Use this functionality to let systemd-tmpfilesd create the static device nodes at boot, and drop the functionality from systemd-udevd. As an effect of this we can move from systemd-udevd to systemd-tmpfiles-setup-dev: * the conditional CAP_MKNOD (replaced by checking if /sys is mounted rw) * ordering before local-fs-pre.target (see 89d09e1b5c65a2d97840f682e0932c8bb499f166)
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-23 05:57:11 +0000