From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libdaemons localstatedir /usr/var
Date: Sun, 12 Oct 2014 09:18:18 +0200 [thread overview]
Message-ID: <20141012091818.04db85ae@free-electrons.com> (raw)
In-Reply-To: <5439D19D.2030706@posteo.de>
Dear J?rg Krause,
On Sun, 12 Oct 2014 02:55:57 +0200, J?rg Krause wrote:
> I have a package which uses libdaemon for running as a daemoon and for
> creating the pid file. libdaemons default directory for opening the pid
> file is /usr/var/run. However, buildroot does not create this directory
> in the output directory by default. The package compiles successfully
> but fails to run because of the missing directory.
>
> How should I deal with this?
>
> 1) patch libdaemon.mk: LIBDAEMON_CONF_OPTS = ... --localstatedir=/var
> 2) add /usr/var/run to my rootfs overlay directory
>
> What do you think? Any other suggestions?
I'd say (1).
Isn't --localstatedir a common autoconf variable ? I see 26 packages
passing --localstatedir=/var in Buildroot. Maybe it's time to move as a
common definition, like --prefix=/usr ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-12 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 0:55 [Buildroot] libdaemons localstatedir /usr/var Jörg Krause
2014-10-12 7:18 ` Thomas Petazzoni [this message]
2014-10-12 9:26 ` Jörg Krause
2014-10-12 13:09 ` Arnout Vandecappelle
2014-10-12 15:56 ` Jörg Krause
2014-10-12 16:13 ` Thomas Petazzoni
2014-10-12 16:18 ` Arnout Vandecappelle
2014-10-17 0:21 ` Jörg Krause
2014-10-17 8:53 ` 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=20141012091818.04db85ae@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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