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 10:35:23 +0200 [thread overview]
Message-ID: <1490776523.6396.407.camel@intel.com> (raw)
In-Reply-To: <20170329072316.GA3298@jama>
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?
--
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.
WARNING: multiple messages have this Message-ID (diff)
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: State of bitbake world, Failed tasks 2017-03-27
Date: Wed, 29 Mar 2017 10:35:23 +0200 [thread overview]
Message-ID: <1490776523.6396.407.camel@intel.com> (raw)
In-Reply-To: <20170329072316.GA3298@jama>
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?
--
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 8:35 UTC|newest]
Thread overview: 11+ 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 ` Patrick Ohly [this message]
2017-03-29 8:35 ` Patrick Ohly
2017-03-29 9:14 ` [OE-core] " Martin Jansa
2017-03-29 9:14 ` Martin Jansa
2017-03-29 9:38 ` [OE-core] " Patrick Ohly
2017-03-29 9:38 ` Patrick Ohly
2017-03-29 10:14 ` [OE-core] " Martin Jansa
2017-03-29 10:14 ` Martin Jansa
2017-03-29 11:19 ` [OE-core] " Patrick Ohly
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=1490776523.6396.407.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.