From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] uclibc: xtensa: fix posix_spawn autoconf detection
Date: Wed, 15 Jan 2014 15:30:33 +0100 [thread overview]
Message-ID: <877ga1uxkm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140115133108.GP4602@tarshish> (Baruch Siach's message of "Wed, 15 Jan 2014 15:31:08 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Hi buildroot list,
> On Mon, Jan 13, 2014 at 08:26:13AM +0200, Baruch Siach wrote:
>> posix_spawn is a new feature in uClibc development branch. Move posix_spawn
>> implementation from librt to libc so that gnulib can detect it correctly.
>>
>> Fixes
>> http://autobuild.buildroot.net/results/ab1/ab1250c3d402ec3fbaf22eeffd07de218ffafb22/.
>>
>> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> Mike Frysinger has rejected this uclibc patch
> (http://article.gmane.org/gmane.comp.lib.gnulib.bugs/33613), but there is a
> different solution suggested for the coreutils build problem
> (http://article.gmane.org/gmane.comp.gnu.coreutils.general/4995). In the mean
> time I'm marking this patch as rejected in patchwork.
Ok, thanks for following up on it.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-01-15 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 6:26 [Buildroot] [PATCH v2 0/3] uclibc: build fixes for xtensa snapshot version Baruch Siach
2014-01-13 6:26 ` [Buildroot] [PATCH v2 1/3] uclibc: bump " Baruch Siach
2014-01-20 21:37 ` Peter Korsgaard
2014-01-13 6:26 ` [Buildroot] [PATCH v2 2/3] uclibc: xtensa: fix posix_spawn autoconf detection Baruch Siach
2014-01-15 13:31 ` Baruch Siach
2014-01-15 14:30 ` Peter Korsgaard [this message]
2014-01-13 6:26 ` [Buildroot] [PATCH v2 3/3] Revert "e2fsprogs: fix posix_fadvise() signature mismatch" Baruch Siach
2014-01-20 21:37 ` Peter Korsgaard
2014-01-13 8:13 ` [Buildroot] [PATCH v2 0/3] uclibc: build fixes for xtensa snapshot version Thomas Petazzoni
2014-01-13 8:23 ` Baruch Siach
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=877ga1uxkm.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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