From: Norbert Lange <nolange79@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] package/lttng-{libust, tools}: use proper systemd rundir
Date: Sat, 27 Jun 2020 00:06:02 +0200 [thread overview]
Message-ID: <20200626220603.29561-4-nolange79@gmail.com> (raw)
In-Reply-To: <20200626220603.29561-1-nolange79@gmail.com>
Set the rundir to /run/lttng, if systemd is the init system.
/var/run is "legacy" in systemd's view.
Perhaps a better way would be to define a variable
BR2_PACKAGE_RUNDIR to /var/run or /run depending on ini system.
(systemd will for example issue warnings for the dbus service,
using a socket in /var/run)
Signed-off-by: Norbert Lange <nolange79@gmail.com>
---
package/lttng-libust/lttng-libust.mk | 4 ++++
package/lttng-tools/lttng-tools.mk | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/package/lttng-libust/lttng-libust.mk b/package/lttng-libust/lttng-libust.mk
index 8e6537690b..f3c660c56f 100644
--- a/package/lttng-libust/lttng-libust.mk
+++ b/package/lttng-libust/lttng-libust.mk
@@ -13,6 +13,10 @@ LTTNG_LIBUST_INSTALL_STAGING = YES
LTTNG_LIBUST_DEPENDENCIES = liburcu util-linux
LTTNG_LIBUST_CONF_OPTS += --disable-man-pages --disable-examples
+ifeq ($(BR2_INIT_SYSTEMD),y)
+LTTNG_LIBUST_CONF_OPTS += --with-lttng-system-rundir=/run/lttng
+endif
+
ifeq ($(BR2_PACKAGE_PYTHON),y)
LTTNG_LIBUST_DEPENDENCIES += python
LTTNG_LIBUST_CONF_OPTS += --enable-python-agent
diff --git a/package/lttng-tools/lttng-tools.mk b/package/lttng-tools/lttng-tools.mk
index b1b0a24a4f..0f3dc84ebd 100644
--- a/package/lttng-tools/lttng-tools.mk
+++ b/package/lttng-tools/lttng-tools.mk
@@ -13,6 +13,10 @@ LTTNG_TOOLS_LICENSE_FILES = LICENSE $(addprefix LICENSES/,BSD-2-Clause BSD-3-Cla
LTTNG_TOOLS_CONF_OPTS += --disable-man-pages
LTTNG_TOOLS_DEPENDENCIES = liburcu libxml2 popt util-linux
+ifeq ($(BR2_INIT_SYSTEMD),y)
+LTTNG_LIBUST_CONF_OPTS += --with-lttng-system-rundir=/run/lttng
+endif
+
ifeq ($(BR2_PACKAGE_LTTNG_LIBUST),y)
LTTNG_TOOLS_CONF_OPTS += --with-lttng-ust
LTTNG_TOOLS_DEPENDENCIES += lttng-libust
--
2.27.0
next prev parent reply other threads:[~2020-06-26 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 22:05 [Buildroot] [PATCH 1/4] package/liburcu: bump version to 0.12.1 Norbert Lange
2020-06-26 22:06 ` [Buildroot] [PATCH 2/4] package/lttng-libust: bump version to 2.12.0 Norbert Lange
2020-06-27 14:45 ` Thomas Petazzoni
2020-06-26 22:06 ` [Buildroot] [PATCH 3/4] package/lttng-tools: bump version to 2.12.1 Norbert Lange
2020-06-27 14:45 ` Thomas Petazzoni
2020-06-26 22:06 ` Norbert Lange [this message]
2020-06-27 14:46 ` [Buildroot] [PATCH 4/4] package/lttng-{libust, tools}: use proper systemd rundir Thomas Petazzoni
2020-06-27 19:32 ` Norbert Lange
2020-06-27 14:45 ` [Buildroot] [PATCH 1/4] package/liburcu: bump version to 0.12.1 Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200626220603.29561-4-nolange79@gmail.com \
--to=nolange79@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox