From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Missing 'sys/queue.h' on musl
Date: Sat, 28 Nov 2015 18:49:15 +0100 [thread overview]
Message-ID: <20151128184915.6017fae9@free-electrons.com> (raw)
In-Reply-To: <CANu7NGtDTbf+0uOcqZQON_E4cwQtRzqiGU=y-NGDe3jjOF0+RQ@mail.gmail.com>
Sergio,
On Sat, 28 Nov 2015 15:31:36 -0200, Sergio Prado wrote:
> Musl does not provide a 'sys/queue.h' implementation [1].
>
> This is causing problems with some packages that depends on it, like
> f2fs-tools [2] and others packages that are already fixed like libtirpc [3].
>
> Adding an implementation of 'sys/queue.h' as a patch (like in [3]) is a
> proper way to fix this problem?
>
> What about creating a package with the 'sys/queue.h' implementation and
> installing it in the staging directory. Then we would just need to make all
> packages that need it depend on it when compiling with musl. Is this a good
> solution?
This seems like a very good idea to me: creating a package that
installs sys/queue.h. It's a lot better than patching all the packages
that use sys/queue.h to make them build with musl.
Do you volunteer to work on this?
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-28 17:49 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 [this message]
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
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=20151128184915.6017fae9@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