Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: limit musl workaround to kernel headers 3.12+
Date: Thu, 01 Jun 2017 16:01:36 +0200	[thread overview]
Message-ID: <8760gfn6wv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <9f5573bb9c8401ad32d34c22c69e062e14b834de.1495167637.git.baruch@tkos.co.il> (Baruch Siach's message of "Fri, 19 May 2017 07:20:37 +0300")

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 > The libc-compat.h first appeared in kernel version 3.12. Trying to build a
 > musl toolchain using earlier headers leads to the following failure:

 > /bin/sed: can't read .../output/host/usr/arm-buildroot-linux-musleabi/sysroot/usr/include/linux/libc-compat.h: No such file or directory
 > package/pkg-generic.mk:266: recipe for target '.../output/build/toolchain/.stamp_staging_installed' failed

 > Don't apply the sed patch to older headers.

 > Reported-by: Florent Jacquet <florent.jacquet@free-electrons.com>
 > Signed-off-by: Baruch Siach <baruch@tkos.co.il>

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2017-06-01 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  4:20 [Buildroot] [PATCH] toolchain: limit musl workaround to kernel headers 3.12+ Baruch Siach
2017-05-19  4:23 ` [Buildroot] Xorg.conf question ? Riko Ho
2017-05-19 10:40 ` [Buildroot] qemu_x86_64_defconfig ==> X11 ? Riko Ho
2017-05-19 13:29 ` [Buildroot] [PATCH] toolchain: limit musl workaround to kernel headers 3.12+ Peter Korsgaard
2017-06-01 14:01 ` Peter Korsgaard [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=8760gfn6wv.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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