summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* Support /proc in _dbus_file_get_contentLuca Boccassi2023-05-151-0/+3
| | | | | | | | | procfs has special semantics: most files are 0 size, only one read can be done on a file, and they are not larger than 4MB. Enhance _dbus_file_get_content() so that we can read files from /proc with it. Signed-off-by: Luca Boccassi <bluca@debian.org>
* Start 1.15.6Simon McVittie2023-02-081-1/+1
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Prepare v1.15.4dbus-1.15.4Simon McVittie2023-02-081-3/+3
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* cleanup: Use gitlab URI for bug reportingMarco Trevisan (Treviño)2022-11-301-1/+1
| | | | Bugzilla is dead for long time now.
* Autotools: use AX_RECURSIVE_EVAL instead of AS_AC_EXPANDSimon McVittie2022-10-121-9/+17
| | | | | | | | | AX_RECURSIVE_EVAL is maintained as part of autoconf-archive, so we don't need to bundle our own copy and keep track of its licensing status. It's very similar to AS_AC_EXPAND, but the arguments are the other way round and it doesn't automatically AC_SUBST its result. Signed-off-by: Simon McVittie <smcv@collabora.com>
* build: Put system bus socket in runstatedir by defaultIssam E. Maghni2022-10-111-7/+2
| | | | | | | | | | | | | | | | | | | | | | This lets OS distributors configure --runstatedir=/run if they want to, although for interoperability, they should only do this if they can guarantee that their /run and /var/run are equivalent. A previous commit adds a warning if we are using the default path on a system where /run and /var/run are not synoymous, mitigating the compatibility impact of this change. For CMake, this requires version 3.9, released in 2017. For Meson, this is currently controlled by the runtime_dir option, which defaults to /run if the prefix is /usr. The rationale for this is that /run is correct for modern Unix systems, and distributors who switch from Autotools or CMake to Meson need to review all their build options at that time, which is an ideal opportunity to check that they are doing the right thing around /run. Helps: https://gitlab.freedesktop.org/dbus/dbus/-/issues/180 Co-authored-by: Simon McVittie <smcv@collabora.com>
* build: Show a warning if the system bus socket is not interoperableSimon McVittie2022-10-111-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | We would like to start using ${runstatedir}/dbus/system_bus_socket, so that distributors who make /var/run a symbolic link to /run will usually get their dbus-daemon listening on /run/dbus/system_bus_socket, which has some advantages in corner cases, such as when /var is mediated by an automounter or is unmounted during system shutdown. Unfortunately, the interoperable path in the D-Bus Specification is /var/run/dbus/system_bus_socket for historical reasons (D-Bus is older than /run), and older versions of Slackware are known to have had /run and /var/run as distinct directories. Do a check during configuration to catch systems configured like this and show a warning. When cross-compiling, this assumes that the system where dbus is built (the build system in Autotools/Meson, or the "host" in CMake terminology) has its /var/run and /run set up in a way that is compatible with the system where dbus will run (the host system in Autotools/Meson, or the "target" in CMake terminology). This is not 100% correct, but seems good enough for a warning that will hopefully only trigger for misguided OS distributors. Signed-off-by: Simon McVittie <smcv@collabora.com>
* build: Update a comment with the release status of AutoconfSimon McVittie2022-10-111-2/+2
| | | | | | It took a while, but Autoconf 2.70 was eventually released. Signed-off-by: Simon McVittie <smcv@collabora.com>
* build: Use AS_IF for system bus socketSimon McVittie2022-10-111-4/+5
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Post-release version bumpSimon McVittie2022-10-051-1/+1
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Prepare v1.15.2dbus-1.15.2Simon McVittie2022-10-051-3/+3
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Post-release version bumpSimon McVittie2022-09-221-1/+1
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Prepare v1.15.0 (development-branch release)Simon McVittie2022-09-221-4/+4
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* dbus-message.c: skip 1.10 layout compatibility test on new architecturesAlex Richardson2022-09-211-1/+6
| | | | | | | These static assertions fail on CHERI-enabled architectures such as Arm Morello, where pointers are 128 bits. Architectures with 128-bit pointers were not supported in DBus 1.10, so we can skip the checks for DBus 1.10 structure layout compatibility for architectures with pointer size > 64 bit.
* dbus-sysdeps-util-unix.c: Avoid including sys/syslimits.hAlex Richardson2022-08-101-1/+0
| | | | | | | This header is GCC specific header that on my system just contains `#include_next <limits.h>`. FreeBSD also provides this header but it contains a `#warning` that it should not be used. Replace the one use with `#include <limit.h>` and drop the configure checks.
* build: Assume stdint.h is providedSimon McVittie2022-07-191-1/+0
| | | | | | | We now require a (mostly-)C99 compiler, meaning we can rely on having Standard C stdint.h. Signed-off-by: Simon McVittie <smcv@collabora.com>
* Remove fallback implementation of strtoll(), strtoull()Simon McVittie2022-07-191-2/+0
| | | | | | | We now require a (mostly-)C99 compiler, which guarantees the presence of these functions. Signed-off-by: Simon McVittie <smcv@collabora.com>
* Remove emulation of va_copy() in non-C99 compilersSimon McVittie2022-07-191-53/+0
| | | | | | | dbus now requires a (mostly-)C99 compiler, which guarantees the presence of Standard C va_copy(). Signed-off-by: Simon McVittie <smcv@collabora.com>
* build: Remove support for emulating inline with __inline or __inline__Simon McVittie2022-07-191-1/+0
| | | | | | | We now require a (mostly-)C99 compiler, and C99 guarantees the presence of the inline keyword. Signed-off-by: Simon McVittie <smcv@collabora.com>
* build-sys: check for afunix.hMarc-André Lureau2022-07-151-0/+8
| | | | Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
* cmake/autotools: remove HAVE_DIRFD/HAVE_DDFDMarc-André Lureau2022-07-131-35/+0
| | | | | | dirfd() is assumed to be present on Linux, dd_fd is never used. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
* configure: Avoid exit() when checking for __sync_sub_and_fetch()Alex Richardson2022-05-261-1/+1
| | | | | | Use of exit() requires a stdlib.h include. This check was failing for me since the compiler defaulted to -Werror=implicit-function-declaration, so __sync_sub_and_fetch() support was not dectected.
* build-sys: console-auth-dir leftoversMarc-André Lureau2022-05-201-1/+0
| | | | Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
* autotools: drop --with-console-auth-dir=Marc-André Lureau2022-05-191-7/+0
| | | | Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
* sysdeps: On Linux, wrap close_range syscall directly if necessarySimon McVittie2022-04-211-0/+1
| | | | | | | | | This was added to the Linux kernel in version 5.9, but the wrapper wasn't added to glibc until 2.34. Adding our own wrapper for the system call means we can use close_range() on Debian 11 and contemporary distributions. Signed-off-by: Simon McVittie <smcv@collabora.com>
* sysdeps: Include <linux/close_range.h> if availableSimon McVittie2022-04-211-0/+1
| | | | | | | This lets us use CLOSE_RANGE_CLOEXEC whenever the kernel headers support it, even if glibc doesn't include this header via unistd.h yet. Signed-off-by: Simon McVittie <smcv@collabora.com>
* sysdeps: Use close_range() if availableSimon McVittie2022-04-211-0/+1
| | | | | | | | | The version with no flags set, which is a slight generalization of closefrom(), is available on recent Linux and FreeBSD. The version with CLOSE_RANGE_CLOEXEC is Linux-specific. Signed-off-by: Simon McVittie <smcv@collabora.com>
* Use closefrom() to not loop over all possible file descriptorsrim2022-04-211-0/+1
| | | | Resolves: https://gitlab.freedesktop.org/dbus/dbus/-/issues/278
* build: Define DBUS_INT64_MODIFIER, analogous to G_GINT64_MODIFIERSimon McVittie2022-04-191-0/+9
| | | | | | | | | | | | | | | | | | | Using PRId64, etc. to print dbus_int64_t or dbus_uint64_t is not 100% portable. On platforms where both long and long long are 64-bit (such as Linux and macOS), we will prefer to define dbus_int64_t as long. If the operating system has chosen to define int64_t as long long, which is apparently the case on macOS, then the compiler can warn that we are passing a long argument to PRId64, which is "lld" and therefore expects a long long argument (even though that ends up with the same bit-pattern being used). We can't necessarily just use int64_t and uint64_t directly, even if all our supported platforms have them available now, because swapping dbus_int64_t between long and long long might change C++ name mangling, causing ABI breaks in third-party libraries if they define C++ functions that take a dbus_int64_t argument. Signed-off-by: Simon McVittie <smcv@collabora.com>
* Convert "if" calls to AS_IF macro for the block that handles X11Lars Wendler2022-03-011-7/+6
|
* Add have_x11=no if --without-x was given to make later checks happyLars Wendler2022-03-011-0/+1
|
* Emit an error when --with-x was given but no X11 libs were foundLars Wendler2022-03-011-6/+7
|
* Move DBUS_X_* definitions into PKG_CHECK_MODULES blockLars Wendler2022-03-011-5/+5
|
* build: Treat --with-x[=yes] the same as --with-x=autoLars Wendler2022-03-011-1/+1
| | | | | Previously, --with-x would disable the check for X11 libraries, which was not intended.
* Post-release version bump for 1.15.xSimon McVittie2022-02-281-3/+3
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Prepare v1.14.0dbus-1.14.0Simon McVittie2022-02-281-4/+4
| | | | | Resolves: https://gitlab.freedesktop.org/dbus/dbus/-/issues/350 Signed-off-by: Simon McVittie <smcv@collabora.com>
* build: Opt out from using mingw-w64's replacement printf(), etc.Simon McVittie2022-02-271-0/+9
| | | | | | | | | | | | | | | The Windows code in dbus is careful to use Windows-specific equivalents of the Standard C features that are not implemented by msvcrt.dll, so we don't need to substitute a Standard C printf implementation. This avoids compiler warnings/errors when gcc expects us to be using Microsoft printf syntax (`ms_printf` attribute), but newer versions of mingw-w64 expect us to be using GNU or Standard C printf syntax (`gnu_printf` attribute) as a result of `__USE_MINGW_ANSI_STDIO` being enabled by default if not otherwise specified. Resolves: https://gitlab.freedesktop.org/dbus/dbus/-/issues/380 Signed-off-by: Simon McVittie <smcv@collabora.com>
* Start development of dbus 1.13.24Simon McVittie2022-02-231-1/+1
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Prepare dbus 1.13.22 and spec 0.38dbus-1.13.22Simon McVittie2022-02-231-3/+3
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Bump version number for continued developmentSimon McVittie2021-12-171-1/+1
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Prepare v1.13.20Simon McVittie2021-12-171-3/+3
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Disable the Containers interfaceSimon McVittie2021-12-101-11/+0
| | | | | | | | We've had a request for a 1.14.x stable-branch, but the Containers interface is only partially implemented, not yet described in the D-Bus Specification, and not ready to be part of our API guarantees. Signed-off-by: Simon McVittie <smcv@collabora.com>
* autotools: use pkg-config instead of AC_PATH_XTRASCOTT-HAMILTON2021-11-261-5/+16
|
* v1.13.18dbus-1.13.18Simon McVittie2020-07-021-3/+3
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Start 1.13.18 developmentSimon McVittie2020-06-021-1/+1
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Prepare 1.13.16dbus-1.13.16Simon McVittie2020-06-021-3/+3
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Add support to generate the api documentation in Qt help formatRalf Habacker2020-04-291-0/+34
| | | | | | | | | Qt help files are used by Qt Creator and KDevelop, for example, to support the development of Qt-based applications and libraries. Generating api documentation in Qt help format is controlled by two user specific options named --enable-qt-help and --with-qchdir (autotools) and -DENABLE_QT_HELP and -DINSTALL_QCH_DIR (cmake).
* Start dbus 1.13.16 developmentSimon McVittie2020-04-211-1/+1
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* Reference implementation v1.13.14 and Specification v0.36dbus-1.13.14Simon McVittie2020-04-211-4/+4
| | | | Signed-off-by: Simon McVittie <smcv@collabora.com>
* _dbus_generate_random_bytes: use getrandom(2)Natanael Copa2020-03-261-0/+2
| | | | | | | | | | Use getrandom(2) and fall back to /dev/urandom if it is missing or if it fails some any reason. This solves problem where dbus-uuidgen is called from a chroot which lacks /dev/urandom. Signed-off-by: Natanael Copa <ncopa@alpinelinux.org>
View Lorry Controller Status