Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libnftnl: exclude for CS PPC toolchains
Date: Tue, 4 Mar 2014 19:38:43 +0100	[thread overview]
Message-ID: <20140304193843.0f42ccd0@skate> (raw)
In-Reply-To: <1393898330-20409-1-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On Mon,  3 Mar 2014 22:58:50 -0300, Gustavo Zacarias wrote:
> The CS PPC 2011.3 and 2010.9 toolchains have a bad linux/socket.h header
> that doesn't define sa_family_t which is used by linux/netlink.h (and
> libnftnl).
> Patching external toolchain headers wouldn't be too nice and they seem
> to be the only CS toolchains affected.
> It's definitely NOT a kernel header version issue, the toolchain is
> based on 2.6.38 headers and vanilla 2.6.38 has the proper definitions in
> place. Fixes:
> http://autobuild.buildroot.net/results/1e2/1e2cac84f0faa9b8915a628260ef41765d86e174/
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  package/libnftnl/Config.in | 2 ++
>  1 file changed, 2 insertions(+)

Not nice to have conditions on specific toolchains, but since the
breakage is specific to them, I guess we don't have much choice.

Thanks, patch applied.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2014-03-04 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  1:58 [Buildroot] [PATCH] libnftnl: exclude for CS PPC toolchains Gustavo Zacarias
2014-03-04 18:38 ` Thomas Petazzoni [this message]

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=20140304193843.0f42ccd0@skate \
    --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