From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-10-15
Date: Sun, 18 Oct 2015 02:48:13 +0200 [thread overview]
Message-ID: <1445129293.7271.17.camel@embedded.rocks> (raw)
In-Reply-To: <20151016063019.E3466101619@stock.ovh.net>
On Fr, 2015-10-16 at 08:30 +0200, Thomas Petazzoni wrote:
> Build statistics for 2015-10-15
> ===============================
>
> Detail of failures
> ===================
>
> ????mips64el |???????????????swupdate-2015.07 | NOK |
> http://autobuild.buildroot.net/results/aaad892a487affe9f62ce4e54ff8bc
> 897f4b99a3/
> ??????x86_64 |???????????????swupdate-2015.07 | NOK | http://autobuil
> d.buildroot.net/results/d9e8298898da6355f6b46a032f951b4ca196d103/
> ????mips64el |???????????????swupdate-2015.07 | NOK | http://autobuil
> d.buildroot.net/results/de3c39640ca972bd3a07e66859f348421342666e/
> ????mips64el |???????????????swupdate-2015.07 | NOK | http://autobuil
> d.buildroot.net/results/d1e446d2c552efd8eb9b34bdc7f50fe7ecccf31c/
Looks related to [1], but I was not able to fix this by changing LD to
gcc instead of ld. But honestly, I am not a toolchain expert and surely
I missed something.
For me it looks like there is a problem with linking the object files
from each 'objs-y' directory into a single object file 'built-in.o'.
A simple solution is to build the subdirectories 'core' and 'handlers'
with the libs-y instead of the objs-y target.
Any thoughts?
[1]?http://git.buildroot.net/buildroot/commit/package/pv?id=1980bf056e1
6c604c1f33ce9771d725da096cfe7
next prev parent reply other threads:[~2015-10-18 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-10-15 Thomas Petazzoni
2015-10-18 0:48 ` Jörg Krause [this message]
2015-10-18 4:57 ` Baruch Siach
2015-10-19 20:48 ` Jörg Krause
2015-10-19 20:49 ` 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=1445129293.7271.17.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