From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libbsd: add upstream patch to fix musl build issue
Date: Mon, 9 Apr 2018 11:25:30 +0200 [thread overview]
Message-ID: <20180409112530.10683cf4@windsurf> (raw)
In-Reply-To: <20180406081835.4239-1-joerg.krause@embedded.rocks>
Hello,
On Fri, 6 Apr 2018 10:18:35 +0200, J?rg Krause wrote:
> Commit d879be3049598f35d7b959784e1a6c2811ba2036 enabled the build for non-glibc
> toolchains and added a patch from upstream to fix one remaining build issue
> with musl.
>
> The upstream patch defines the glibc specific macro `__GLIBC_PREREQ` in
> `include/bsd/sys/cdefs.h`, but the patch does not include this header
> file in `include/bsd/stdlib.h` which uses the macro.
>
> Upstream did committed an earlier patch which adds this header inclusion
> to `include/bsd/stdlib.h`. So, add this upstream patch as well to fix a
> build error when building the hcitop tool from the not yet added package
> bluez-alsa.
>
> Note, that the upstream patch address the issue that `<sys/cdefs.h>` is
> a non-portable header. However, this is not the issue which needs to be
> fixed by this patch, but solely the needed inclusion of the
> `include/bsd/stdlib.h` header file, to see the definition of
> `__GLIBC_PREREQ`.
>
> Backported from: 11ec8f1e5dfa1c10e0c9fb94879b6f5b96ba52dd
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> ...3-Handle-systems-missing-sys-cdefs.h.patch | 230 ++++++++++++++++++
> 1 file changed, 230 insertions(+)
> create mode 100644 package/libbsd/0003-Handle-systems-missing-sys-cdefs.h.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-04-09 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 8:18 [Buildroot] [PATCH] libbsd: add upstream patch to fix musl build issue Jörg Krause
2018-04-06 8:52 ` Thomas Petazzoni
2018-04-06 10:21 ` Jörg Krause
2018-04-09 9:25 ` 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=20180409112530.10683cf4@windsurf \
--to=thomas.petazzoni@bootlin.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.