All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] toolchain: workaround musl/kernel headers conflict
Date: Thu, 18 May 2017 09:10:30 +0200	[thread overview]
Message-ID: <20170518091030.66a9cbee@free-electrons.com> (raw)
In-Reply-To: <20170518045754.ecwqdtj35acvzk6b@tarshish>

Hello,

On Thu, 18 May 2017 07:57:54 +0300, Baruch Siach wrote:

> I have not tested kernel headers earlier than v3.12. Having a look at the 
> headers and the log of kernel commit cfd280c91253cc28 (net: sync some IP 
> headers with glibc), I'm pretty sure that the same issue also affects older 
> kernels.
> 
> Should we just disallow build of musl toolchain with older kernels? Something 
> like:

That's one option, though a bit annoying, no? Just for this "small"
reason, we prevent people from using musl toolchains on kernels older
than 3.12 ?

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

  reply	other threads:[~2017-05-18  7:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 13:27 [Buildroot] [PATCH v2 1/3] toolchain: workaround musl/kernel headers conflict Baruch Siach
2016-11-10 13:27 ` [Buildroot] [PATCH v2 2/3] Revert "bridge-utils: fix build with musl" Baruch Siach
2016-11-10 13:27 ` [Buildroot] [PATCH v2 3/3] Revert "norm: add patch to fix musl build" Baruch Siach
2016-11-13 21:33 ` [Buildroot] [PATCH v2 1/3] toolchain: workaround musl/kernel headers conflict Arnout Vandecappelle
2016-11-15 22:33   ` Thomas Petazzoni
2016-11-16 15:45     ` Baruch Siach
2016-11-16 15:55       ` Thomas Petazzoni
2016-11-16 16:25         ` Baruch Siach
2016-11-16 16:36           ` Thomas Petazzoni
2016-11-16 20:43             ` Baruch Siach
2016-11-16 22:30 ` Thomas Petazzoni
2017-05-17 13:33 ` Thomas Petazzoni
2017-05-18  4:57   ` Baruch Siach
2017-05-18  7:10     ` Thomas Petazzoni [this message]
2017-05-18 11:17       ` Baruch Siach
2017-05-18 11:24         ` Thomas Petazzoni
2017-05-18 11:37           ` Baruch Siach

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=20170518091030.66a9cbee@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.