Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

[Marek Vasut]

On 03/16/2018 10:21 AM, auh@auh.yoctoproject.org wrote:
> Hello,

Hi,

> 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 ?

-- 
Best regards,
Marek Vasut

Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

[Alexander Kanavin]

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

Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

[Marek Vasut]

On 03/19/2018 09:50 AM, Alexander Kanavin wrote:
> 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?

I was hoping the tool will take care of that, now that I've finally
plucked all the extra patches out.

-- 
Best regards,
Marek Vasut

Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

[Alexander Kanavin]

On 03/19/2018 11:55 AM, Marek Vasut wrote:

>> 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?
> 
> I was hoping the tool will take care of that, now that I've finally
> plucked all the extra patches out.

You can automate most of the upgrade by running 'devtool upgrade u-boot' 
though. Extra patches are not a problem for automatic updates. If U-BOOT 
and qemu can be made friends, that's even better.

Alex

Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

[Marek Vasut]

On 03/19/2018 10:57 AM, Alexander Kanavin wrote:
> On 03/19/2018 11:55 AM, Marek Vasut wrote:
> 
>>> 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?
>>
>> I was hoping the tool will take care of that, now that I've finally
>> plucked all the extra patches out.
> 
> You can automate most of the upgrade by running 'devtool upgrade u-boot'
> though. Extra patches are not a problem for automatic updates. If U-BOOT
> and qemu can be made friends, that's even better.

So what's the problem with qemu and u-boot ? I don't see why it couldn't
be built for qemu targets.

-- 
Best regards,
Marek Vasut

Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

[Alexander Kanavin]

On 03/19/2018 12:08 PM, Marek Vasut wrote:
>>>> 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?
>>>
>>> I was hoping the tool will take care of that, now that I've finally
>>> plucked all the extra patches out.
>>
>> You can automate most of the upgrade by running 'devtool upgrade u-boot'
>> though. Extra patches are not a problem for automatic updates. If U-BOOT
>> and qemu can be made friends, that's even better.
> 
> So what's the problem with qemu and u-boot ? I don't see why it couldn't
> be built for qemu targets.

Maybe, but right now it's not working, and it's something the u-boot 
experts should tackle and test.

ak@kanavin-desktop:~/development/poky/build$ bitbake u-boot
Loading cache: 100% 
|##########################################################################################################################################################################################################################| 
Time: 0:00:00
Loaded 1310 entries from dependency cache.
ERROR: Nothing PROVIDES 'u-boot'
u-boot was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in 
the qemux86 machine configuration.


I do see that u-boot has qemu configs though:

http://git.denx.de/?p=u-boot.git;a=tree;f=configs;h=a6603a9f312f1e86fa233adf21a51a2c7cf46653;hb=HEAD

Alex

Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

[Marek Vasut]

On 03/19/2018 11:31 AM, Alexander Kanavin wrote:
> On 03/19/2018 12:08 PM, Marek Vasut wrote:
>>>>> 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?
>>>>
>>>> I was hoping the tool will take care of that, now that I've finally
>>>> plucked all the extra patches out.
>>>
>>> You can automate most of the upgrade by running 'devtool upgrade u-boot'
>>> though. Extra patches are not a problem for automatic updates. If U-BOOT
>>> and qemu can be made friends, that's even better.
>>
>> So what's the problem with qemu and u-boot ? I don't see why it couldn't
>> be built for qemu targets.
> 
> Maybe, but right now it's not working, and it's something the u-boot
> experts should tackle and test.
> 
> ak@kanavin-desktop:~/development/poky/build$ bitbake u-boot
> Loading cache: 100%
> |##########################################################################################################################################################################################################################|
> Time: 0:00:00
> Loaded 1310 entries from dependency cache.
> ERROR: Nothing PROVIDES 'u-boot'
> u-boot was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in
> the qemux86 machine configuration.

Try building with UBOOT_MACHINE = "qemu-x86_defconfig" .

> I do see that u-boot has qemu configs though:
> 
> http://git.denx.de/?p=u-boot.git;a=tree;f=configs;h=a6603a9f312f1e86fa233adf21a51a2c7cf46653;hb=HEAD

Yes

-- 
Best regards,
Marek Vasut

Re: [AUH] u-boot-mkimage: upgrading to 2018.03 FAILED

[Alexander Kanavin]

On 03/19/2018 12:53 PM, Marek Vasut wrote:
> Try building with UBOOT_MACHINE = "qemu-x86_defconfig" .

| unable to execute 'swig': No such file or directory
| error: command 'swig' failed with exit status 1


Alex