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 1/1] netcat-openbsd: depends on linux-headers >= 3.12
Date: Sun, 31 Dec 2017 14:16:19 +0100	[thread overview]
Message-ID: <20171231141619.11116894@windsurf> (raw)
In-Reply-To: <20171128154437.1631-1-gael.portay@savoirfairelinux.com>

Hello,

On Tue, 28 Nov 2017 10:44:37 -0500, Ga?l PORTAY wrote:
> This debian fork of netcat includes the kernel UAPI inet6 header. This
> header conflicts with the existing libc inet header and causes
> redefinition of structures when they are both included.
> 
> The compiler raises the following error:
> 
> 	/home/buildroot/build/instance-0/output/host/x86_64-buildroot-linux-gnu/sysroot/usr/include/linux/in6.h:30:8: error: redefinition of 'struct in6_addr' struct in6_addr {
> 
> From version 3.12 of linux, the kernel UAPI header has mechanisms in
> libc-compat.h to prevent such situations (see __UAPI_DEF_SOCKADDR_IN6
> macros).
> 
> Unfortunately the build is broken when toolchains do not satisfy at least
> the linux headers condition (>= 3.12).
> 
> The package now depends on the toolchain headers at least 3.12.
> 
> Signed-off-by: Ga?l PORTAY <gael.portay@savoirfairelinux.com>
> ---

You forgot to update the Config.in comment, so I've done so, and
applied your patch. Thanks!

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

      parent reply	other threads:[~2017-12-31 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 15:44 [Buildroot] [PATCH 1/1] netcat-openbsd: depends on linux-headers >= 3.12 Gaël PORTAY
2017-11-29 21:24 ` Thomas Petazzoni
2017-11-30 17:10   ` Baruch Siach
2017-11-30 19:36     ` Thomas Petazzoni
2017-11-30 19:53       ` Baruch Siach
2017-11-30 19:57       ` Gaël PORTAY
2017-12-31 13:16 ` 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=20171231141619.11116894@windsurf \
    --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