From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Missing 'sys/queue.h' on musl
Date: Sun, 29 Nov 2015 09:28:11 +0100 [thread overview]
Message-ID: <20151129092811.0d05dabd@free-electrons.com> (raw)
In-Reply-To: <CANu7NGvmMFc9xADTq_ES7h=13LcnLH5yYJO9KV+8mSYSB-VVtg@mail.gmail.com>
Hello,
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?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-29 8:28 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 [this message]
2015-11-29 9:53 ` Yann E. MORIN
2015-11-29 22:14 ` Arnout Vandecappelle
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=20151129092811.0d05dabd@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