From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-03-15
Date: Mon, 16 Mar 2015 23:17:03 +0100 [thread overview]
Message-ID: <20150316231703.329d6f87@free-electrons.com> (raw)
In-Reply-To: <CAMo8BfKuPTASXR9JEx=aGctfNxNcr2PDewyS+GGt6jcbeY8dbw@mail.gmail.com>
Dear Max Filippov,
On Tue, 17 Mar 2015 01:02:28 +0300, Max Filippov wrote:
> On Mon, Mar 16, 2015 at 10:30 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > xtensa | libnl-3.2.25 | NOK | http://autobuild.buildroot.net/results/90c318e3a9ef5e626d0a80e36695d34eda21f97e/
> > xtensa | memcached-1.4.22 | NOK | http://autobuild.buildroot.net/results/cd8e9d9a5f454c321071c21192958aeee9c39e73/
>
> Caused by disabled UCLIBC_HAS_GNU_GETSUBOPT option in the uclibc config.
> Also reproducible with other architectures that use uclibc.
> I guess we can just enable it in the config, additional code is really small.
On libnl, the error only happened twice, and only on xtensa:
http://autobuild.buildroot.org/?reason=libnl-3.2.25. What's weird is
that in uClibc-0.9.33.config, which we use on other architectures, we
also have UCLIBC_HAS_GNU_GETSUBOPT disabled. But still there is a
getsubopt symbol in the generated uClibc .so file.
Needs more investigation, it seems.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-16 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-03-15 Thomas Petazzoni
2015-03-16 22:02 ` Max Filippov
2015-03-16 22:17 ` Thomas Petazzoni [this message]
2015-03-16 22:29 ` Max Filippov
2015-03-16 22:56 ` Max Filippov
2015-03-16 23:49 ` Max Filippov
-- strict thread matches above, loose matches on Subject: below --
2015-03-16 19:48 Peter Seiderer
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=20150316231703.329d6f87@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox