Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-02-27
Date: Sat, 05 Mar 2016 21:10:07 +0100	[thread overview]
Message-ID: <1457208607.1867.7.camel@embedded.rocks> (raw)
In-Reply-To: <56D385A7.9050804@mind.be>

On Mo, 2016-02-29 at 00:41 +0100, Arnout Vandecappelle wrote:
> 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/2061238affb685db99
> > > > > 8100a56c6571538d089a5b/
> > > > > 
> > > > > ?> /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...

Building czmq with the latest git HEAD does not throw this error
anymore.

Although, for the current version 3.0.2 disabling the optional binaries
zmakecert and zgossip also helps to build libczmq.la cleanly without
the need to link libmath in. I've sent a patch to disable building both
binaries by default [1].

[1]?http://patchwork.ozlabs.org/patch/592453/

Best regards
J?rg Krause

  reply	other threads:[~2016-03-05 20:10 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
2016-03-05 20:10             ` Jörg Krause [this message]
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=1457208607.1867.7.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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