From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/eflutils: needs argp-standalone with musl toolchains
Date: Mon, 3 Aug 2015 11:15:04 +0200 [thread overview]
Message-ID: <20150803111504.65278b31@free-electrons.com> (raw)
In-Reply-To: <1438448118-26198-2-git-send-email-romain.naour@openwide.fr>
Dear Romain Naour,
On Sat, 1 Aug 2015 18:55:17 +0200, Romain Naour wrote:
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> ---
> package/elfutils/Config.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/elfutils/Config.in b/package/elfutils/Config.in
> index 6c6856e..ea0ae62 100644
> --- a/package/elfutils/Config.in
> +++ b/package/elfutils/Config.in
> @@ -4,7 +4,7 @@ comment "elfutils needs a toolchain w/ wchar, dynamic library"
>
> config BR2_PACKAGE_ELFUTILS
> bool "elfutils"
> - select BR2_PACKAGE_ARGP_STANDALONE if BR2_TOOLCHAIN_USES_UCLIBC
> + select BR2_PACKAGE_ARGP_STANDALONE if BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_MUSL
This is not sufficient to get elfutils to build with musl. Lots of
other changes are needed (TEMP_FAILURE_RETRY, <error.h>, etc.).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-03 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 16:55 [Buildroot] [PATCH 1/3] package/rng-tools: needs argp-standalone with musl toolchains Romain Naour
2015-08-01 16:55 ` [Buildroot] [PATCH 2/3] package/eflutils: " Romain Naour
2015-08-02 15:26 ` Yann E. MORIN
2015-08-03 9:15 ` Thomas Petazzoni [this message]
2015-08-01 16:55 ` [Buildroot] [PATCH 3/3] package/libv4l: " Romain Naour
2015-08-02 15:29 ` Yann E. MORIN
2015-08-03 9:16 ` Thomas Petazzoni
2015-08-03 16:27 ` Yann E. MORIN
2015-08-02 15:25 ` [Buildroot] [PATCH 1/3] package/rng-tools: " 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=20150803111504.65278b31@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