Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Gaël PORTAY" <gael.portay@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] netcat-openbsd: depends on linux-headers >= 3.12
Date: Thu, 30 Nov 2017 14:57:02 -0500	[thread overview]
Message-ID: <20171130195702.va3cwfbz5zhe2scp@archlinux> (raw)
In-Reply-To: <20171130203625.28575e36@windsurf.lan>

Thomas,

On Thu, Nov 30, 2017 at 08:36:25PM +0100, Thomas Petazzoni wrote:
> Hello,
> 
> On Thu, 30 Nov 2017 19:10:49 +0200, Baruch Siach wrote:
> 
> > On Wed, Nov 29, 2017 at 10:24:35PM +0100, Thomas Petazzoni wrote:
> > > Since you have looked at a lot of different kernel headers related
> > > issues, what do you think about this one below?  
> > 
> > Makes sense. We have faced the same issue with musl and iproute2. In each of 
> > these cases we used different solutions because both provide their own 
> > headers. For the simple case, it is reaonable to limit build to toolchains 
> > with newer kernel headers providing libc-compat.h.
> > 
> > Reviewed-by: Baruch Siach <baruch@tkos.co.il>
> 
> Well, what bothers me is that netcat is a fairly simple tool, so I find
> it odd that we restrict it to >= 3.12.
>

If you prefer, I can update debian patch to not include the kernel UAPI
header.

It will compile, but this version of netcat will be "amputated" from
ipv6 feature.

Gael

  parent reply	other threads:[~2017-11-30 19:57 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 [this message]
2017-12-31 13:16 ` 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=20171130195702.va3cwfbz5zhe2scp@archlinux \
    --to=gael.portay@savoirfairelinux.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