From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Missing 'sys/queue.h' on musl
Date: Sun, 29 Nov 2015 23:14:48 +0100 [thread overview]
Message-ID: <565B78D8.6070103@mind.be> (raw)
In-Reply-To: <20151129095306.GA3630@free.fr>
On 29-11-15 10:53, Yann E. MORIN wrote:
> Thomas, All,
>
> On 2015-11-29 09:28 +0100, Thomas Petazzoni spake thusly:
>> On Sat, 28 Nov 2015 18:42:37 -0200, Sergio Prado wrote:
>>> Instead of making each package that needs 'sys/queue.h' select this
>>> package, it would be better to select this package automatically when a
>>> musl toolchain is used. That way, we won't need to change any package.
>>>
>>> It is possible to do that?
>>
>> Well, we could probably put this logic in the toolchain virtual
>> package, since it is the common point between the internal toolchain
>> and external toolchain backends (and we need sys/queue.h in both cases).
>>
>> However, I am not sure if I wouldn't prefer packages that need
>> sys/queue.h to have an explicit dependency on the package installing
>> sys/queue.h. Since such package would itself have no dependency, it
>> would be just a matter of adding "select BR2_PACKAGE_SYS_QUEUE" in
>> Config.in and adding "sys-queue" in <pkg>_DEPENDENCIES.
>>
>> Peter, Arnout, Yann, your opinion?
>
> I think it is best to handle it as a dependency of the toolchain
> package. That way, it is transparent to packages.
>
> That musl refuses to carry a sys/queue.h on philosophical reasons (as
> they explain in their FAQ) while all the other main C libraries do (even
> newlib!) is not ground for making it difficult for packagers to add a
> new package.
>
> Adding such a package would be a Buildroot peculiarity, which I would
> prefer we avoid.
+1 to that.
Also take into account that we only install it to staging, so there is really
nothing to gain from installing it conditionally.
The only question is whether to do it in the toolchain virtual package (which
would be unusual to say the least), or duplicate it in the musl and external
toolchain packages. I actually think the latter is the way to go.
When adding this, there's a small issue to take into account: a
buildroot-generated musl toolchain will already have queue.h, so for the
external toolchain support you probably have to check if it exists already in
the toolchain itself.
Regards,
Arnout
>
> Regards,
> Yann E. MORIN.
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-29 22:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 17:31 [Buildroot] Missing 'sys/queue.h' on musl Sergio Prado
2015-11-28 17:49 ` Thomas Petazzoni
2015-11-28 18:18 ` Sergio Prado
2015-11-28 18:20 ` Thomas Petazzoni
2015-11-28 20:42 ` Sergio Prado
2015-11-29 8:28 ` Thomas Petazzoni
2015-11-29 9:53 ` Yann E. MORIN
2015-11-29 22:14 ` Arnout Vandecappelle [this message]
2015-11-29 22:33 ` Thomas Petazzoni
2015-11-30 10:16 ` Sergio Prado
2015-11-30 10:54 ` Peter Korsgaard
2015-11-30 15:07 ` Sergio Prado
2015-11-30 16:32 ` Thomas Petazzoni
2015-11-30 21:34 ` Arnout Vandecappelle
2015-11-30 22:56 ` Sergio Prado
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=565B78D8.6070103@mind.be \
--to=arnout@mind.be \
--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