From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-04
Date: Wed, 5 Nov 2014 13:46:14 +0000 [thread overview]
Message-ID: <545A2A26.8060506@imgtec.com> (raw)
In-Reply-To: <20141105073015.758941014DB@stock.ovh.net>
Dear all,
On 11/05/2014 07:30 AM, Thomas Petazzoni wrote:
> mipsel | civetweb-v1.5 | NOK | http://autobuild.buildroot.net/results/4a179bebdc9cd85780d7f16f672ee019a1947147/
The external toolchain used here doesn't have the needed fix in order to
build civetweb for uClibc + static. This has been already fixes in
Buildroot but this toolchain was generated before.
Patch sent: http://patchwork.ozlabs.org/patch/406989/
> mipsel | coreutils-8.23 | NOK | http://autobuild.buildroot.net/results/2f2f298c9baccba79d7c94a02703be708cec6757/
"makeinfo: command not found"
This fails when generating the documentation because the build host
doesn't have texinfo installed (which provides the makeinfo tool).
However, using the same exact configuration and removing the makeinfo
executable from my system, I still being unable to reproduce this failure.
> mipsel | rt-tests-0.83 | NOK | http://autobuild.buildroot.net/results/9bfb9bcad67727bdaf74c94206eca0bb728d7eec/
> mipsel | rt-tests-0.83 | NOK | http://autobuild.buildroot.net/results/b64a150f3e66d6f2504d2b28f2594e67eda8ea16/
This shouldn't be happening. The rt-tests package should be removed from
the build list for the toolchains used in those config files. The
builder who did those builds doesn't have an updated autobuild-run script.
ThomasP in CC.
> arm | sdl_sound-1.0.3 | NOK | http://autobuild.buildroot.net/results/aa4dc974c297ad2595363ee524a18ea30536cca1/
Reported upstream:
http://lists.libsdl.org/pipermail/sdl-libsdl.org/2014-November/096804.html
Related: http://patchwork.ozlabs.org/patch/400969/
> mips64el | znc-b396cafdb249544164ed029... | TIM | http://autobuild.buildroot.net/results/d777f62139f47677becd41c76c9ed4a02ff3301d/
This seems an error of the autobuilder. The compilation stops suddenly
without any error message.
Best regards,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
prev parent reply other threads:[~2014-11-05 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-04 Thomas Petazzoni
2014-11-05 13:46 ` Vicente Olivert Riera [this message]
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=545A2A26.8060506@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