From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-19
Date: Wed, 21 May 2014 23:27:54 +0200 [thread overview]
Message-ID: <537D1A5A.1000000@mind.be> (raw)
In-Reply-To: <20140520092513.0ad98a62@free-electrons.com>
On 20/05/14 09:25, Thomas Petazzoni wrote:
> On Tue, 20 May 2014 08:30:07 +0200 (CEST), Thomas Petazzoni wrote:
>
>> > x86_64 | alsa-lib-1.0.26 | NOK | http://autobuild.buildroot.net/results/3ecb780be9e7912dac9670d9e7ad9a810c6243af/
> Multiple definitions of vfork in libc.a and libpthread.a. To me, this
> looks like a uClibc bug. Do other agree about this? Should we mark
> alsa-lib as not available on pure static builds with uClibc? Is there a
> uClibc patch that fixes that?
When I did that allpackageyes of a static arm configuration, there were dozens
of packages that show the same or a similar problem (duplicates in libpthread
and libc). I looked at one of them in more detail, and I could make it link by
playing around with the link options, but I haven't been able to find the real
cause.
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
prev parent reply other threads:[~2014-05-21 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-19 Thomas Petazzoni
2014-05-20 7:25 ` Thomas Petazzoni
2014-05-20 7:41 ` Peter Korsgaard
2014-05-21 21:27 ` Arnout Vandecappelle [this message]
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=537D1A5A.1000000@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 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.