Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] libdaemons localstatedir /usr/var
Date: Sun, 12 Oct 2014 18:18:02 +0200	[thread overview]
Message-ID: <543AA9BA.5020807@mind.be> (raw)
In-Reply-To: <20141012181317.6ad4ba95@free-electrons.com>

On 12/10/14 18:13, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Sun, 12 Oct 2014 17:56:02 +0200, J?rg Krause wrote:
>
> >>>      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...
>
> If you add that to host configure, it should be $(HOST_DIR)/var.

 But I don't think that there's any host package that does anything
useful with the localstatedir.

 Regards,
 Arnout

>
> Thomas
>


-- 
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-10-12 16: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
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 [this message]
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=543AA9BA.5020807@mind.be \
    --to=arnout@mind.be \
    --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