Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] libdaemons localstatedir /usr/var
Date: Sun, 12 Oct 2014 17:56:02 +0200	[thread overview]
Message-ID: <543AA492.2080907@posteo.de> (raw)
In-Reply-To: <543A7D79.7010008@mind.be>


On 10/12/2014 03:09 PM, Arnout Vandecappelle wrote:
> On 12/10/14 11:26, J?rg Krause wrote:
>> Dear Thomas Petazzoni,
>>
>> On 10/12/2014 09:18 AM, Thomas Petazzoni wrote:
>>> 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).
>> Looks good. I will prepare a patch.
>>
>>> 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 ?
>> Yes, it is. There was a discussion on the mailing list long time ago:
>>
>>      Making --localstatedir=/var global?
>>      (http://lists.busybox.net/pipermail/buildroot/2011-April/042918.html.)
>>
>> And also this one:
>>
>>      Bizarre things on the allyespackageconfig build
>>      (http://lists.busybox.net/pipermail/buildroot/2013-May/071856.html)
>   +1 to making it a global pkg-autotools option. J?rg, care to prepare a patch
> for that? Removing the existing --localstatedir should be a separate patch then.

I will prepare a patch for this. Should I add this to host configure, 
too? I guess so...

  reply	other threads:[~2014-10-12 15:56 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
2014-10-12  9:26   ` Jörg Krause
2014-10-12 13:09     ` Arnout Vandecappelle
2014-10-12 15:56       ` Jörg Krause [this message]
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=543AA492.2080907@posteo.de \
    --to=jkrause@posteo.de \
    --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