From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED
Date: Mon, 19 Mar 2018 10:50:43 +0200 [thread overview]
Message-ID: <caedac22-09fe-1ee3-34c7-8e285743f352@linux.intel.com> (raw)
In-Reply-To: <8f7b8f66-1a17-6051-e626-fc4a3d26c5af@gmail.com>
On 03/17/2018 06:27 PM, Marek Vasut wrote:
>> You are receiving this email because you are the maintainer
>> of *u-boot-mkimage* recipe and this is to let you know that the automatic attempt
>> to upgrade the recipe to *2018.03* has Failed(do_compile).
>>
>> Detailed error information:
>>
>> do_compile failed
>
> It seems this only bumped some of the U-Boot recipes to 2018.03 while it
> left some at 2018.01, so it's not really surprising it failed. Maybe
> this is an auto-update bug ?
The problem is that AUH is using qemu machines to determine what needs
to be updated, and to attempt building new versions. u-boot is not
enabled in qemu at all, and so it's skipped:
ERROR: Nothing PROVIDES 'u-boot'
u-boot was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in
the qemux86 machine configuration.
I'm not sure how to solve it - perhaps you can simply take the email as
a reminder to update the whole set on your machine manually?
Alex
next prev parent reply other threads:[~2018-03-19 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180316092125.64DD7440071@auh.yoctoproject.org>
2018-03-17 16:27 ` [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED Marek Vasut
2018-03-19 8:50 ` Alexander Kanavin [this message]
2018-03-19 9:55 ` Marek Vasut
2018-03-19 9:57 ` Alexander Kanavin
2018-03-19 10:08 ` Marek Vasut
2018-03-19 10:31 ` Alexander Kanavin
2018-03-19 10:53 ` Marek Vasut
2018-03-19 10:53 ` Alexander Kanavin
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=caedac22-09fe-1ee3-34c7-8e285743f352@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=marek.vasut@gmail.com \
--cc=openembedded-core@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