From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix compilation of systemd with uclibc
Date: Thu, 3 Oct 2013 09:13:12 +0200 [thread overview]
Message-ID: <20131003091312.6fba7e5e@skate> (raw)
In-Reply-To: <524CFDF9.3090807@mind.be>
Dear Arnout Vandecappelle,
On Thu, 03 Oct 2013 07:17:45 +0200, Arnout Vandecappelle wrote:
> > Yeah, it would add a lot of complexity. Another option is to make such
> > packages non-selectable if an external uClibc toolchain is used.
>
> But that means that the typical scenario for a uClibc-based toolchain
> won't work (use buildroot or ct-ng to generate a toolchain once, and
> import it as an external toolchain).
Yes, indeed.
There's not much we can do here: the uClibc community is so slow at
producing releases that many projects backport a lot of features and
fixes, and therefore from one toolchain to another, the "uClibc 0.9.33"
that you get might be quite different.
While we can certainly require the external toolchains to have a
uClibc configuration that has at least the same features as the
Buildroot uClibc configuration, it seems hard to require those
external toolchains to have in their uClibc a feature that has never
been part of a uClibc release (which is the case of the execvpe being
discussed in this thread).
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-03 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 11:38 [Buildroot] [PATCH] Fix compilation of systemd with uclibc Jérôme Pouiller
2013-10-01 12:40 ` Thomas Petazzoni
2013-10-02 15:02 ` Peter Korsgaard
2013-10-02 15:12 ` Thomas Petazzoni
2013-10-02 16:43 ` Arnout Vandecappelle
2013-10-02 21:17 ` Thomas Petazzoni
2013-10-03 5:17 ` Arnout Vandecappelle
2013-10-03 7:13 ` Thomas Petazzoni [this message]
2013-10-27 11:35 ` Arnout Vandecappelle
2013-10-27 12:54 ` Eric Le Bihan
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=20131003091312.6fba7e5e@skate \
--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