From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-08-04
Date: Tue, 5 Aug 2014 14:03:12 +0100 [thread overview]
Message-ID: <53E0D610.3070603@imgtec.com> (raw)
In-Reply-To: <20140805063010.EAA98100F1D@stock.ovh.net>
On 08/05/2014 07:30 AM, Thomas Petazzoni wrote:
> Build statistics for 2014-08-04
> ===============================
> mips64el | python3-3.4.1 | NOK | http://autobuild.buildroot.net/results/31a9cf4152aca7ba7d5ab798eea3161a9e47e68d/
That build failure is caused because in that toolchain...
http://autobuild.buildroot.org/toolchains/tarballs/mips64el-ctng_n64-linux-gnu.tar.x
...SYS_getdents64 is only defined for MIPS32 and MIPS64 n32, and NOT for
MIPS64 n64.
That has been fixed on newer versions of eglibc (which is the C library
that toolchain is using). For instance, in the Buildroot's default
eglibc version (2.18-svnr23787) it's already fixed.
So, please, could be possible to upgrade that toolchain.
Thanks.
--
Vincent
next prev parent reply other threads:[~2014-08-05 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-08-04 Thomas Petazzoni
2014-08-05 13:03 ` Vicente Olivert Riera [this message]
2014-08-05 14:17 ` 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=53E0D610.3070603@imgtec.com \
--to=vincent.riera@imgtec.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