Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix compilation of systemd with uclibc
Date: Wed, 02 Oct 2013 18:43:19 +0200	[thread overview]
Message-ID: <524C4D27.9030601@mind.be> (raw)
In-Reply-To: <20131001144009.4117ea4c@skate>

On 10/01/13 14:40, Thomas Petazzoni wrote:
> Dear J?r?me Pouiller,
>
> On Tue,  1 Oct 2013 13:38:12 +0200, J?r?me Pouiller wrote:
>> systemd-uclibc-fix.patch was applied to systemd to provide execvpe function
>> when compiled with uclibc. However, this function is now provided by
>> libc-add-non-standard-execvpe-function.patch in uclibc package.
>>
>> These two patchs are now in conflict. This commit remove
>> systemd/systemd-uclibc-fix.patch.
>
> The thing that worries me is that we start to rely on uClibc features
> that are provided by specific patches we have added to our uClibc
> package. This means that an user using an uClibc toolchain provided by
> Analog Devices for Blackfin, or built with Crosstool-NG will no longer
> work properly to build those packages.
>
> I'm not sure what to do about this, though. Mark those packages as
> available only with glibc or the internal uClibc toolchain? Stop
> backporting uClibc feature patches (like we do for other packages) and
> tell people to work with upstream uClibc to get things fixed and
> released?

  We could make kconfig options for them and verify them in 
$sysroot/include/bits/uClibc_config.h. Or, in the case of execvpe which 
doesn't have a kconfig option, verify in $sysroot/include/unistd.h. But 
it's adding a lot of complexity.


  Regards,
  Arnout


-- 
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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2013-10-02 16:43 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 [this message]
2013-10-02 21:17     ` Thomas Petazzoni
2013-10-03  5:17       ` Arnout Vandecappelle
2013-10-03  7:13         ` Thomas Petazzoni
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=524C4D27.9030601@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