summaryrefslogtreecommitdiff
path: root/Makefile.am
Commit message (Collapse)AuthorAgeFilesLines
* test-efi-create-disk.sh: allow running from separate build dir, hook up to mesonZbigniew Jędrzejewski-Szmek2017-04-231-2/+2
| | | | | | This allow test-efi-disk.img to be created under meson. The invocation of qemu is not converted yet, in particular because the command-line used in Makefile.am is outdated.
* meson: add hwdb/update targetZbigniew Jędrzejewski-Szmek2017-04-231-12/+2
|
* journal/fsprg: set -Wno-pointer-arithm only for that fileZbigniew Jędrzejewski-Szmek2017-04-231-3/+1
| | | | | | | | | | Both gcc and clang issue a host of warnings about void pointers used in arithmetic. The warning must be ignored in that file to avoid multiple warnings. Makefile.am used to set this for all libsystemd-journal-internal.a sources, because there's no finer granularity for warnings. Let's just set it for this one file.
* Makefile.am: remove duplicated rules for efiZbigniew Jędrzejewski-Szmek2017-04-211-26/+15
| | | | | | | | Specifying the same rule with a slightly different dep list was not useful, since make cannot distinguish rules with the same input / output. (It possibly could have two rules with different dependency list, but here all dependencies that are different between the two rules are always present, so the two rules are effectively the same.)
* Makefile.am: link dbus-org.freedesktop.network1 alias in /etcZbigniew Jędrzejewski-Szmek2017-04-191-4/+2
| | | | | This makes dbus-org.freedesktop.network1.service like dbus-org.freedesktop.resolve1.service. When systemd-networkd.service is disabled, the alias is also removed.
* Merge pull request #5708 from vcatechnology/arm-cross-compileLennart Poettering2017-04-171-0/+5
|\ | | | | ARM32 cross-compile fixes
| * build-sys: correct ARM32 GNU EFI boot binary buildMatt Clarkson2017-04-061-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | Due to ARM not having an EFI capable objcopy we need to use the binary output argument. This is correctly set up for AArch64 but is missed when building for ARM32. This patch adds the ARCH_ARM automake define which can then be used in the makefile to determine if to use the correct linker flags. The addition of the ARM32 flags is a copy and paste from the AArch64 to create a logical OR for the ARCH_AARCH64 and ARCH_ARM variables. I couldn't figure out a better way to create the conditional with basic Make language constructs.
* | build-sys: drop obsolete hook from Makefile.amZbigniew Jędrzejewski-Szmek2017-04-041-3/+0
| |
* | udev: rename gperf struct name to match other headersZbigniew Jędrzejewski-Szmek2017-04-041-1/+1
| | | | | | | | | | | | | | This makes it easier to use the same generator script as for other gperf scripts. With automake each gperf file had it's own rule, but with meson I'm trying to use one script, and this inconsistency made that harder.
* | tree-wide: standardize on $(PACKAGE_VERSION) for the version stringZbigniew Jędrzejewski-Szmek2017-04-041-4/+3
| | | | | | | | | | | | We defined both $(VERSION) and $(PACKAGE_VERSION) with the same contents. $(PACKAGE_VERSION) is slightly more descriptive, so settle on that, and drop the other define.
* | build-sys: drop undefined target ref from Makefile.amZbigniew Jędrzejewski-Szmek2017-04-041-2/+0
| |
* | build-sys: drop undefined var ref from Makefile.amZbigniew Jędrzejewski-Szmek2017-04-041-4/+0
| |
* | Move busctl sources to src/busctlZbigniew Jędrzejewski-Szmek2017-04-041-3/+3
| | | | | | | | | | | | busctl is not part of libsystemd, and should not be stored under libsystemd. In particular this is confusing because busctl is linked with libshared, but stuff in libsystemd is not supposed to depend on libshared.
* | test-sizeof: do not link with libsystemd-sharedZbigniew Jędrzejewski-Szmek2017-03-291-3/+0
| | | | | | | | This makes it much quicker to compile.
* | rules: add a rule to set /dev/kvm access mode and ownership (#5597)Zbigniew Jędrzejewski-Szmek2017-03-271-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Kernel default mode is 0600, but distributions change it to group kvm, mode either 0660 (e.g. Debian) or 0666 (e.g. Fedora). Both approaches have valid reasons (a stricter mode limits exposure to bugs in the kvm subsystem, a looser mode makes libvirt and other virtualization mechanisms work out of the box for unprivileged users over ssh). In Fedora the qemu package carries the relevant rule, but it's nicer to have it in systemd, so that the permissions are not dependent on the qemu package being installed. Use of packaged qemu binaries is not required to make use of /dev/kvm, e.g. it's possible to use a self-compiled qemu or some alternative. https://bugzilla.redhat.com/show_bug.cgi?id=1431876 To accomodate both approaches, add a rule to set the mode in 50-udev-default.rules, but allow the mode to be overridden with a --with-dev-kvm-mode configure rule. The default is 0660, as the (slightly) more secure option.
* | basic: don't link "libm.so" into "libbasic.so" (#5628)Thomas Haller2017-03-241-2/+1
| | | | | | | | | | | | | | Very few parts of the systemd source require <math.h> or "libm.so". Linking libbasic with -lm drags the mathematical library in for all systemd components, and in turn for all users of systemd libraries. It's just unneeded.
* | units: simplify rescue.service and emergency.service (#5623)Michael Biebl2017-03-221-0/+10
| | | | | | | | | | | | | | The emergency.service and rescue.service units have become rather convoluted. We spawn multiple shells and the help text spans multiple lines which makes the units hard to read. Move the logic into a single shell script and call that via ExecStart.
* | build-sys: minor indentation fixMichael Biebl2017-03-221-1/+1
| |
* | build-sys: make RPM macros installation path configurable (#5564)steelman2017-03-141-1/+5
| | | | | | --with-rpmmacrosdir=no disables installation of the macros.
* | build-sys: add helper command to sign tarballsZbigniew Jędrzejewski-Szmek2017-03-111-0/+3
| |
* | build-sys: simplify git tar invocationZbigniew Jędrzejewski-Szmek2017-03-111-1/+1
| | | | | | | | | | git is nowadays nice enough to compress based on the output file suffix, let's make use of that.
* | build-sys: make more targets .PHONYZbigniew Jędrzejewski-Szmek2017-03-111-0/+3
| |
* | build-sys: only install legacy *.pkla files with old polkit versions (#5555)Martin Pitt2017-03-081-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | The legacy *.pkla files are not required when running against polkit ≥ 106, and we want to avoid shipping files in /var if possible (but pkla files can only be in /etc/ or /var). Only install the *.pkla files if we detect an old polkit version during configure. Don't install them if polkit isn't installed during build, as distributions other than Debian-based ones have moved to the new polkit long ago. Fixes #5523
* | sd-bus: drop kdbus-related docs (#5533)AsciiWolf2017-03-071-3/+0
| |
* | Avoid strict DM interface version dependencies (#5519)Michael Biebl2017-03-021-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Compiling against the dm-ioctl.h header as provided by the Linux kernel will embed the DM interface version number. Running an older kernel can result in an error like this on shutdown: Could not detach DM dm-11: ioctl mismatch, kernel(4.34.4), user(4.35.4) Work around this by shipping a local copy of dm-ioctl.h. We need at least the version from 3.13 for DM_DEFERRED_REMOVE [1], so bump the requirements in README accordingly. [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2c140a246dc0bc085b98eddde978060fcec1080c Fixes: #5492
* | build-sys: do not require everything to be rebuild to push man pages (#5521)Zbigniew Jędrzejewski-Szmek2017-03-021-1/+1
| | | | | | When the doc-sync target was created, we didn't have man target yet.
* | Revert "environment.d: fix date"Zbigniew Jędrzejewski-Szmek2017-03-011-1/+1
| | | | | | | | | | | | This reverts commit 46987593ccb1c78f3889ea91a0c94f9cc810d43c. Pushed to the wrong repo, sorry.
* | environment.d: fix dateZbigniew Jędrzejewski-Szmek2017-03-011-1/+1
|/
* journalctl: move access_check() to shared/Zbigniew Jędrzejewski-Szmek2017-02-281-0/+2
| | | | | | | | | | | The only functional change is that log_notice("No journal files were found.") is not printed any more with --quiet. log_error("No journal files were opened due to insufficient permissions.") is still printed. I wasn't quite sure where to put this function, but shared/ seems to be the right place and none of the existing files seem to fit too well. v2: rename journal_access_check to journal_access_check_and_warn.
* Revert "udev: Introduce UDEV_PROPAGATE_LOG macro (#5302)"Lennart Poettering2017-02-231-22/+1
| | | | | | | This reverts commit c22569eeeafa94cf510267071f5b75c4ab714e09. Let's revert this for now, since it apparently doesn't fix the problem at hand.
* Revert "Makefile.am: add a `\` (#5422)"Lennart Poettering2017-02-231-5/+5
| | | | This reverts commit 00d1e0c9def4557c74f46cc2fe3a7ebc32a1dc8a.
* Makefile.am: add a `\` (#5422)Susant Sahani2017-02-211-5/+5
| | | fixes: #5419
* udev: Introduce UDEV_PROPAGATE_LOG macro (#5302)Susant Sahani2017-02-221-1/+22
| | | | | | | | | | | | | | | As per commit 25e773e "udev: switch to systemd logging functions" Now log_set_max_level() in udev_new() overwites system wide log level. Propagate the udev.conf setting to log_set_max_level() only if udev_new() is called from within udevd or one of its helpers. Introduce a UDEV_PROPAGATE_LOG macro that we set with -D on the gcc command line for all udev binaries we build, but not for any others. The log_set_max_level() call is guarded by an ifdef check for that macro, so that it only effects the various udev binaries. closes: #4525
* build-sys: bump package versionLennart Poettering2017-02-211-3/+3
|
* Merge pull request #5131 from keszybz/environment-generatorsLennart Poettering2017-02-211-3/+41
|\ | | | | Environment generators
| * build-sys: make environment.d support conditionalZbigniew Jędrzejewski-Szmek2017-02-201-3/+7
| | | | | | | | | | | | We have ./configure switches for various parts of non-essential functionality, let's add one for this new stuff too. Support for environment generators is not conditional — if you don't want them, just don't install any.
| * build-sys,man: load /etc/environment and describe the new environment.d syntaxRay Strode2017-02-201-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | Add support for /etc/environment and document the changes to the user manager to automatically import environment *.conf files from: ~/.config/environment.d/ /etc/environment.d/ /run/environment.d/ /usr/local/lib/environment.d/ /usr/lib/environment.d/ /etc/environment
| * environment-generator: new generator to peruse environment.dZbigniew Jędrzejewski-Szmek2017-02-201-0/+10
| | | | | | | | | | | | | | | | Why the strange name: the prefix is necessary to follow our own advice that environment generators should have numerical prefixes. I also put -d- in the name because otherwise the name was very easy to mistake with systemd.environment-generator. This additional letter clarifies that this on special generator that supports environment.d files.
| * man: add systemd.environment-generator(7) with two examplesZbigniew Jędrzejewski-Szmek2017-02-201-1/+3
| | | | | | | | | | | | | | | | | | v2: - add example files to EXTRA_DIST v3: - rework for the new scheme where nothing is written to disk v4: - use separate dirs for system and user env generators
| * manager: run environment generatorsZbigniew Jędrzejewski-Szmek2017-02-201-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Environment file generators are a lot like unit file generators, but not exactly: 1. environment file generators are run for each manager instance, and their output is (or at least can be) individualized. The generators themselves are system-wide, the same for all users. 2. environment file generators are run sequentially, in priority order. Thus, the lifetime of those files is tied to lifecycle of the manager instance. Because generators are run sequentially, later generators can use or modify the output of earlier generators. Each generator is run with no arguments, and the whole state is stored in the environment variables. The generator can echo a set of variable assignments to standard output: VAR_A=something VAR_B=something else This output is parsed, and the next and subsequent generators run with those updated variables in the environment. After the last generator is done, the environment that the manager itself exports is updated. Each generator must return 0, otherwise the output is ignored. The generators in */user-env-generator are for the user session managers, including root, and the ones in */system-env-generator are for pid1.
| * basic/util: move execute_directory() to separate fileZbigniew Jędrzejewski-Szmek2017-02-111-0/+9
| | | | | | | | It's a fairly specialized function. Let's make new files for it and the tests.
* | units: enable resolved bus activation though a symlink in /etcLennart Poettering2017-02-171-4/+2
| | | | | | | | | | | | | | | | | | The change: -/usr/lib/systemd/system/dbus-org.freedesktop.resolve1.service +/etc/systemd/system/dbus-org.freedesktop.resolve1.service If resolved is disabled, without this, talking to the resolved bus API will activate it regardless whether it is enabled or not, let's fix that.
* | Merge pull request #5338 from mbiebl/fix-install-tests-targetEvgeny Vereshchagin2017-02-171-6/+7
|\ \ | | | | | | Fix "make install-tests" when srcdir != builddir, fix valgrind-tests
| * | build-sys: drop now-unneeded $SYSTEMD_TEST_DATA when running testsZbigniew Jędrzejewski-Szmek2017-02-171-1/+0
| | |
| * | tests: look for tests relative to source dir when running from build dirZbigniew Jędrzejewski-Szmek2017-02-161-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | automake helpfully sets a few variables for during build. When our executable is in a directory underneath $(abs_top_builddir), we know that we're in the build environment $(abs_top_srcdir) contains the sources, and test data is under $(abs_top_srcdir)/test. This remains true no matter where the build directory is relative to the source directory. It also works if the test executable is invoked as ./test-whatever or .libs/test-whatever, since the relative path is not used at all. When running from outside of the build directory, we should be running from the installed location and we can look for ../testdata relative to the location of the exe file. Of course, $SYSTEMD_TEST_DATA always overrides this logic.
| * | Rename $TEST_DIR to $SYSTEMD_TEST_DATA, document itZbigniew Jędrzejewski-Szmek2017-02-161-1/+1
| | | | | | | | | | | | | | | TEST_DIR is rather generic, and we prefix all variables used by installed executables with "SYSTEMD_".
| * | test: run valgrind-tests under $TESTS_ENVIRONMENTMartin Pitt2017-02-161-1/+1
| | | | | | | | | | | | | | | Otherwise we are missing $TEST_DIR for the test data and run the test against the system-installed binaries and keyboard/locale maps.
| * | build-sys: fix "make install-tests" when srcdir != builddirMichael Biebl2017-02-161-4/+4
| | | | | | | | | | | | Follow-up for 4f8425b8d5a3fb2e5ec24b77f1a7a95db55f532c
* | | build-sys: add exec-privatedevices-[yes|no]-capability-sys-rawio to ↵Evgeny Vereshchagin2017-02-161-0/+2
| | | | | | | | | | | | | | | | | | TEST_DATA_FILES This is a follow-up for 625d8769fa6394a30
* | | build-sys: treat journal-data/journal-[12].txt as TEST_DATA_FILESEvgeny Vereshchagin2017-02-161-1/+1
|/ / | | | | | | | | | | | | | | | | | | Fixes: ``` Found container virtualization none. Assertion 'imp.fd >= 0' failed at ../src/test/test-journal-importer.c:43, function test_basic_parsing(). Aborting. FAIL: test-journal-importer (code: 134) ``` See https://github.com/systemd/systemd/pull/5366#issuecomment-280353804
View Lorry Controller Status