From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-02-27
Date: Mon, 29 Feb 2016 00:41:27 +0100 [thread overview]
Message-ID: <56D385A7.9050804@mind.be> (raw)
In-Reply-To: <1456674270.13955.11.camel@embedded.rocks>
On 02/28/16 16:44, J?rg Krause wrote:
> On So, 2016-02-28 at 16:06 +0100, Arnout Vandecappelle wrote:
>> On 02/28/16 12:17, J?rg Krause wrote:
>>>
>>> On So, 2016-02-28 at 10:42 +0100, Peter Korsgaard wrote:
>>>>>>>>> "J?rg" == J?rg Krause <joerg.krause@embedded.rocks>
>>>>>>>>> writes:
>>>> > On So, 2016-02-28 at 08:30 +0100, Thomas Petazzoni wrote:
>>>> >>
>>>> >> powerpc | czmq-v3.0.2 | NOK |
>>>> >> http://autobuild.buildroot.net/results/2061238affb685db998100a56c6571538d089a5b/
>>>>
>>>> > /home/test/autobuild/instance-3/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib/libstdc++.a(compatibility-ldbl.o): In function `std::tr1::hash<long double>::operator()(long double) const':
>>>> > compatibility-ldbl.cc:(.text._ZNKSt3tr14hashIeEclEe+0x3c): undefined reference to `frexpl'
>>>>
>>>> > I cannot reproduce it on my 64-bit host.
[snip]
> That's why I sent a patch with LIBS=-lm.
The problem turns out to be more complicated... It's actually a problem with
libstdc++. Dependeing on the arch, some functions will be in
compatibility-ldbl.o. If you use any of these functions, that file will be
linked in. And when that file is linked in, all the _other_ functions, which you
actually don't use, are also linked in. And one of these functions is the
template function hash<long double>::operator(), which uses frexpl.
So, requiring czmq to link with -lm is a bit weird, given that neither itself,
nor any of its dependencies really need it...
So ideally it should be fixed in libstdc++ itself. But I have no idea how to do
that...
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-28 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-02-27 Thomas Petazzoni
2016-02-28 9:25 ` Jörg Krause
2016-02-28 9:42 ` Peter Korsgaard
2016-02-28 10:28 ` Jörg Krause
2016-02-28 11:17 ` Jörg Krause
2016-02-28 15:06 ` Arnout Vandecappelle
2016-02-28 15:44 ` Jörg Krause
2016-02-28 23:41 ` Arnout Vandecappelle [this message]
2016-03-05 20:10 ` Jörg Krause
2016-03-05 20:26 ` Thomas Petazzoni
2016-03-06 9:47 ` Jörg Krause
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=56D385A7.9050804@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