From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/iputils: patch ping to link against libm
Date: Tue, 16 Feb 2016 21:30:23 +0100 [thread overview]
Message-ID: <20160216213023.14b06e86@free-electrons.com> (raw)
In-Reply-To: <CAFGQKxdemRmCT51fvTuTOeYWeOv9y3Tv2nY=wUdpVKtePUf0bQ@mail.gmail.com>
Hello,
On Tue, 16 Feb 2016 19:58:13 +0000, Martin Bark wrote:
> I can't reproduce the issues you see. I just ran some more tests and
> for me iputils fails with undefined reference to `__finite' when built
> against uClibc regardless of BR2_ENABLE_DEBUG=y. I had a defconfig
> with only BR2_PACKAGE_IPUTILS=y.
>
> I looked at the autobuild fails for iputils from here
> http://autobuild.buildroot.org/?reason=iputils-c8ff6feaf0442f8efd96ccb415770c54f9e84d47
> and there are lots of fails without BR2_ENABLE_DEBUG=y
All failures occur with the internal toolchain backend, i.e when using
the latest uClibc-ng version. So it seems to me that the failure
started to exist in a recent uClibc-ng version: the pre-built uClibc
toolchains that are based on uClibc-ng 1.0.9 do not exhibit the problem.
> > The finite macros where added here:
> > http://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/include/math.h?id=21902b578e96fd6b85b9bcda8a0e929fc844ec51
> > So 1.0.10 is the first release containing this BSD specific
> > functions in a usable way.
Which would probably match with Waldemar's change in 1.0.10.
Waldemar, can you conrfirm? If those functions are only available
starting in 1.0.10, how can iputils build with 1.0.9 ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-16 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 13:00 [Buildroot] [PATCH 1/1] package/iputils: patch ping to link against libm Martin Bark
2016-02-15 22:17 ` Thomas Petazzoni
2016-02-16 10:13 ` Martin Bark
2016-02-16 19:03 ` Waldemar Brodkorb
2016-02-16 19:58 ` Martin Bark
2016-02-16 20:30 ` Thomas Petazzoni [this message]
2016-02-16 20:28 ` Thomas Petazzoni
2016-02-17 0:17 ` Arnout Vandecappelle
2016-02-17 7:56 ` Thomas Petazzoni
2016-02-20 14:51 ` Thomas Petazzoni
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=20160216213023.14b06e86@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.