From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libbsd: enable for non-glibc toolchains
Date: Sat, 31 Mar 2018 22:52:10 +0200 [thread overview]
Message-ID: <20180331225210.3082b688@windsurf> (raw)
In-Reply-To: <20180314194356.15839-1-joerg.krause@embedded.rocks>
Hello,
On Wed, 14 Mar 2018 20:43:56 +0100, J?rg Krause wrote:
> libbsd builds now almost fine with a musl or uClibc toolchain, except
> for one issue introduced in the latest version bump. Upstream commit
> 22fbd62368c39de8ac5e249d1502d5ac0ffdef30 [1] uses the glibc-only macro
> `__GLIBC_PREREQ`. The issue is fixed by the attached patch from upstream,
> which fixes the use of `__GLIBC_PREREQ` on non-glibc toolchains.
>
> Backported from:
> https://cgit.freedesktop.org/libbsd/patch/?id=1f8a3f7bccfc84b195218ad0086ebd57049c3490
>
> netcat-openbsd is the only package selecting libbsd. However, building
> it still needs a glibc toolchain, as it uses `b64_ntop` which is not
> available in musl or uClibc.
>
> Build has been successfully tested with:
> * armv7-eabihf--glibc--bleeding-edge-2017.11-1
> * armv7-eabihf--musl--bleeding-edge-2018.02-1
> * armv7-eabihf--uclibc--bleeding-edge-2018.02-1
>
> [1] https://cgit.freedesktop.org/libbsd/commit/?id=22fbd62368c39de8ac5e249d1502d5ac0ffdef30
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> ...n-declaration-protection-for-glibc-alread.patch | 80 ++++++++++++++++++++++
> package/libbsd/Config.in | 5 +-
> 2 files changed, 82 insertions(+), 3 deletions(-)
> create mode 100644 package/libbsd/0001-Fix-function-declaration-protection-for-glibc-alread.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-31 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 19:43 [Buildroot] [PATCH] package/libbsd: enable for non-glibc toolchains Jörg Krause
2018-03-14 21:09 ` Thomas Petazzoni
2018-03-14 21:13 ` Jörg Krause
2018-03-15 2:57 ` Thomas Petazzoni
2018-03-31 20:52 ` Thomas Petazzoni [this message]
2018-04-02 12:34 ` Yann E. MORIN
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=20180331225210.3082b688@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox