From: Patrick Ohly <patrick.ohly@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] State of bitbake world, Failed tasks 2017-03-27
Date: Wed, 29 Mar 2017 11:38:38 +0200 [thread overview]
Message-ID: <1490780318.6396.410.camel@intel.com> (raw)
In-Reply-To: <20170329091444.GB3298@jama>
On Wed, 2017-03-29 at 11:14 +0200, Martin Jansa wrote:
> On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:
> > On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> > > INFO: jenkins-job.sh-1.8.19 Complete log available at http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
> >
> > That used OE-core 552bd78, if I read this right:
> >
> > == Tested changes (not included in master yet) - openembedded-core ==
> > latest upstream commit:
> > 552bd78 wic: use kernel_dir to find systemd-efi bootloader
> >
> > > * openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:do_compile
> >
> > http://errors.yoctoproject.org/Errors/Details/135202/
> >
> > "gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6
> > "fix toolchain selection", which is included in OE-core 552bd78 and thus
> > should have been included in the build.
> >
> > However, the error above was "Submitted on: 11/03/17 10:13", which was a
> > while ago and in particular before that fix.
> >
> > Did ovmf really fail in the latest world build?
>
> The report shows:
> http://errors.yoctoproject.org/Errors/Build/34933/
> which leads to:
>
> http://errors.yoctoproject.org/Errors/Details/138261/
> Submitted on: 27/03/17 05:31
Got it. I followed the wrong link at some point.
> So yes it failed again, but this time with different error:
> TOPDIR/tmp-glibc/work/i586-oe-linux/ovmf/git-r0/recipe-sysroot-native/usr/bin/i586-oe-linux/../../libexec/i586-oe-linux/gcc/i586-oe-linux/6.3.0/ld:
> internal error in do_layout, at ../../gold/object.cc:1821
Hmm, internal error in gold. Not sure what to do about that :-/
Can individual recipes choose to be built using the normal ld?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-03-29 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 7:23 State of bitbake world, Failed tasks 2017-03-27 Martin Jansa
2017-03-29 8:35 ` [OE-core] " Patrick Ohly
2017-03-29 9:14 ` Martin Jansa
2017-03-29 9:38 ` Patrick Ohly [this message]
2017-03-29 10:14 ` Martin Jansa
2017-03-29 11:19 ` Patrick Ohly
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=1490780318.6396.410.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/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