From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: fix duplicate vfork problems when static linking
Date: Sun, 7 Sep 2014 11:07:36 +0200 [thread overview]
Message-ID: <20140907110736.7bb9919e@free-electrons.com> (raw)
In-Reply-To: <20140901200606.GA14078@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Mon, 1 Sep 2014 22:06:06 +0200, Waldemar Brodkorb wrote:
> Reported on uClibc mailinglist by Thomas Petazzoni
> Should fix:
> * SuperH
> http://autobuild.buildroot.org/results/a81/a810c2f27dee1978808461c05cbdcbf51a214e09/build-end.log
> * i386
> http://autobuild.buildroot.org/results/f83/f83b65bfc6ea7c7406a02e92afda43e4c5db6e7c/build-end.log
> * x86-64
> http://autobuild.buildroot.org/results/64f/64f418f54885e8b5093dc8949c2d1d1ff3c938ea/build-end.log
> * powerpc
> http://autobuild.buildroot.org/results/d5b/d5b7ac84dde0e4e26cd7cc46d79e66c39ed5cd53/build-end.log
>
> Tested with i386 static build of alsa-utils.
> Patch will be send to uClibc soon, need to finish test-suite run.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> ...nptl-remove-duplicate-vfork-in-libpthread.patch | 691 ++++++++++++++++++++
> 1 file changed, 691 insertions(+)
> create mode 100644 package/uclibc/0.9.33.2/uclibc-0062-nptl-remove-duplicate-vfork-in-libpthread.patch
Thanks a lot for working on this!
Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
(Built tested on i386, x86-64 and PowerPC. Statically linking alsa-lib
now works fine. I didn't test SuperH because our internal toolchain
backend is currently broken for SuperH.)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-07 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 20:06 [Buildroot] [PATCH] uclibc: fix duplicate vfork problems when static linking Waldemar Brodkorb
2014-09-07 9:07 ` Thomas Petazzoni [this message]
2014-09-14 20:59 ` Peter Korsgaard
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=20140907110736.7bb9919e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.