From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libnspr: disable for musl toolchains
Date: Sat, 29 Aug 2015 20:18:41 +0200 [thread overview]
Message-ID: <20150829201841.227bc47d@free-electrons.com> (raw)
In-Reply-To: <1440870131-17263-1-git-send-email-romain.naour@openwide.fr>
Dear Romain Naour,
On Sat, 29 Aug 2015 19:42:11 +0200, Romain Naour wrote:
> libnspr use getprotobyname_r() which is not available on musl.
>
> Also there is another error due to missing _PR_HAVE_GETHOSTBYNAME2 define:
> prnetdb.c: In function ?PR_GetIPNodeByName?:
> prnetdb.c:898:2: error: #error "Unknown name-to-address translation function"
> #error "Unknown name-to-address translation function"
>
> _PR_HAVE_GETHOSTBYNAME2 is only set in pr/include/md/_linux.h if __GLIBC__
> is defined.
>
> To conclude, libnspr is not ready for musl.
> Add reverse dependency on ecryptfs-utils and libnss.
>
> Fixes:
> http://autobuild.buildroot.net/results/c75/c756f82dfc49611fa3f650d9cf2a71b59d23c3d0/
>
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
Could you instead give a try to
http://git.alpinelinux.org/cgit/aports/tree/main/nspr/fix-getproto.patch ?
Generally speaking, for musl compatibility issues, always look at
http://git.alpinelinux.org/cgit/aports/tree/main/, it very often
contains interesting patches.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-29 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 17:42 [Buildroot] [PATCH] package/libnspr: disable for musl toolchains Romain Naour
2015-08-29 18:18 ` Thomas Petazzoni [this message]
2015-08-29 18:36 ` Romain Naour
2015-12-24 10:21 ` 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=20150829201841.227bc47d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox