From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-05-19
Date: Tue, 26 May 2015 07:11:50 +0000 [thread overview]
Message-ID: <1432624310.2727.5.camel@synopsys.com> (raw)
In-Reply-To: <20150520231825.240a9292@free-electrons.com>
Hi Thomas,
On Wed, 2015-05-20 at 23:18 +0200, Thomas Petazzoni wrote:
> > arc | libedbus-1.7.10 | NOK | http://autobuild.buildroot.net/results/4a0b4db5fdad581e1ec3e8133bfdb1c485105a65/
>
> uClibc bug in static linking:
>
> multiple definition of `__GI_raise'
>
> Alexey, can you have a look and see if it's fixed in uClibc master?
Looks like that's a generic problem with statically built uClibc with
Linuxthreads.old
In case of NPTL "libc/signals/raise.c" won't be compiled so there's no
even possibility for such a clash.
We'll take a look at that problem, still since we're moving toward NPTL
tools if there's no simple solution we may just leave it as it is now
until there's anybody interested in fixing that for good.
-Alexey
prev parent reply other threads:[~2015-05-26 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-05-19 Thomas Petazzoni
2015-05-20 21:18 ` Thomas Petazzoni
2015-05-21 6:55 ` Jörg Krause
2015-05-26 7:11 ` Alexey Brodkin [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=1432624310.2727.5.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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