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 15:54:59 -0300	[thread overview]
Message-ID: <54592103.30908@zacarias.com.ar> (raw)
In-Reply-To: <20141104192043.03f7159b@free-electrons.com>

On 11/04/2014 03:20 PM, Thomas Petazzoni wrote:

> There was a patch from Bernd, a759931c9b0cb4337dc30fd35d03ce123271c5a4,
> which made libcap depend on headers >= 3.7. But I reverted it in
> d5146f4b53d926c13a47215ac514e43b2c66b9ac, because Bernd's analysis was
> not correct, and libcap did not depend on kernel headers >= 3.7.
> 
> Are you sure 3.1 is really the correct starting point? Here is what I
> wrote at the time:

Yes, true, the definition moved to another header from 2.6.35 -> 2.6.36
The failure seems to affect only the 2011 cs lite ppc toolchain.
Even though it's based on 2.6.38 headers something bad was done to it:

freescale-2011.03 $ find . -type f -exec grep --with-filename
XATTR_NAME_CAPS {} \; -> nothing (yes i did '-name *.h' first but to my
amazement nothing returned so i went all-out).

So as a POC i've built a 2.6.35.14-based basic toolchain with libcap
enabled and everything went fine.

My professional opinion is that the codesourcery powerpc 2011.03
toolchain is messed up.
So we either blacklist it or do users a favor and just deprecate/remove it.
Regards.

  reply	other threads:[~2014-11-04 18:54 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
2014-11-04 18:20           ` Thomas Petazzoni
2014-11-04 18:54             ` Gustavo Zacarias [this message]
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=54592103.30908@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