Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Samba4 build issue
Date: Tue, 04 Nov 2014 11:01:54 -0300	[thread overview]
Message-ID: <5458DC52.6020706@zacarias.com.ar> (raw)
In-Reply-To: <20141104082623.33a2136e@free-electrons.com>

On 11/04/2014 04:26 AM, Thomas Petazzoni wrote:

> Dear Gustavo Zacarias,
> 
> On Sun, 02 Nov 2014 09:51:11 -0300, Gustavo Zacarias wrote:
>> On 11/02/2014 06:38 AM, Thomas Petazzoni wrote:
>>
>>> Ok, so it's libcap causing issues. Have those issues reported upstream?
>>> While reverting to an older version libcap being an acceptable
>>> temporary workaround, it's not going to be nice on the long run;
>>
>> They're fixed, revised patch sent.
>> Let's just hope it doesn't break other stuff.
> 
> Great, thanks for having worked on this.

D'oh!
http://autobuild.buildroot.net/results/992/9928a251e5cfcf6e574a447221e938135eeb69f9/build-end.log
Seems the new libcap version requires 3.1+ kernel headers.
I'm not a big fan of those ppc toolchains since they're old, but what's
the linux headers baseline we're looking for?

Mandatory use of libcap:
cdrkit - ouch
lxc - probably not that much
squid - probably not that much
systemd - irrelevant, needs newer headers by itself

We could propagate the headers dep, it's just that it will look silly on
cdrkit.
Opinions?

Regards.

  reply	other threads:[~2014-11-04 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 22:39 [Buildroot] Samba4 build issue Thomas Petazzoni
2014-11-02  0:16 ` Gustavo Zacarias
2014-11-02  9:38   ` Thomas Petazzoni
2014-11-02 12:51     ` Gustavo Zacarias
2014-11-04  7:26       ` Thomas Petazzoni
2014-11-04 14:01         ` Gustavo Zacarias [this message]
2014-11-04 18:20           ` Thomas Petazzoni
2014-11-04 18:54             ` Gustavo Zacarias
2014-11-05  7:13               ` 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=5458DC52.6020706@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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