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

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

[Marek Vasut]

On 05/17/2018 04:13 AM, auh@auh.yoctoproject.org wrote:
> Hello,
> 
> 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.05* has Failed(do_compile).
> 
> Detailed error information:
> 
> do_compile failed

Well yeah, if you dont upgrade all the recipes, it'll fail ...

-- 
Best regards,
Marek Vasut

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

[Alexander Kanavin]

On 05/17/2018 12:56 PM, Burton, Ross wrote:
> Looks like AUH runs as a x86 machine, which is why it doesn't catch u-boot.

Also we have already discussed this 2 month ago. Marek, as the u-boot 
maintainer, can you look into enabling u-boot on qemu please?

Alex

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

[Burton, Ross]

Looks like AUH runs as a x86 machine, which is why it doesn't catch u-boot.

Ross

On 17 May 2018 at 10:40, Marek Vasut <marek.vasut@gmail.com> wrote:
> On 05/17/2018 04:13 AM, auh@auh.yoctoproject.org wrote:
>> Hello,
>>
>> 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.05* has Failed(do_compile).
>>
>> Detailed error information:
>>
>> do_compile failed
>
> Well yeah, if you dont upgrade all the recipes, it'll fail ...
>
> --
> Best regards,
> Marek Vasut

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

[Marek Vasut]

On 05/17/2018 11:53 AM, Alexander Kanavin wrote:
> On 05/17/2018 12:56 PM, Burton, Ross wrote:
>> Looks like AUH runs as a x86 machine, which is why it doesn't catch
>> u-boot.
> 
> Also we have already discussed this 2 month ago. Marek, as the u-boot
> maintainer, can you look into enabling u-boot on qemu please?

Wouldn't it make more sense to fix the AUH so it handles U-Boot and
similar packages correctly even without the qemu dependency ?

-- 
Best regards,
Marek Vasut

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

[Burton, Ross]

u-boot is excluded on the machine type that the AUH runs as, so
there's no way it can build the recipe.

Ross

On 17 May 2018 at 11:33, Marek Vasut <marek.vasut@gmail.com> wrote:
> On 05/17/2018 11:53 AM, Alexander Kanavin wrote:
>> On 05/17/2018 12:56 PM, Burton, Ross wrote:
>>> Looks like AUH runs as a x86 machine, which is why it doesn't catch
>>> u-boot.
>>
>> Also we have already discussed this 2 month ago. Marek, as the u-boot
>> maintainer, can you look into enabling u-boot on qemu please?
>
> Wouldn't it make more sense to fix the AUH so it handles U-Boot and
> similar packages correctly even without the qemu dependency ?
>
> --
> Best regards,
> Marek Vasut

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

[Alexander Kanavin]

On 05/17/2018 01:33 PM, Marek Vasut wrote:
>>> Looks like AUH runs as a x86 machine, which is why it doesn't catch
>>> u-boot.
>>
>> Also we have already discussed this 2 month ago. Marek, as the u-boot
>> maintainer, can you look into enabling u-boot on qemu please?
> 
> Wouldn't it make more sense to fix the AUH so it handles U-Boot and
> similar packages correctly even without the qemu dependency ?

Determining the latest upstream version, performing the recipe upgrade, 
and testing that the upgraded version builds are all done by calling 
bitbake. Which of course requires that MACHINE is set to something 
specific, in this case qemux86. As u-boot is disabled there, it gets 
skipped. I could special-case u-boot, but I do think it's better to 
enable it on qemu, which would also allow better AB testing across 
architectures and during runtime (booting images) for instance.

Alex

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

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 679 bytes --]

On Thu, May 17, 2018 at 12:33:24PM +0200, Marek Vasut wrote:
> On 05/17/2018 11:53 AM, Alexander Kanavin wrote:
> > On 05/17/2018 12:56 PM, Burton, Ross wrote:
> >> Looks like AUH runs as a x86 machine, which is why it doesn't catch
> >> u-boot.
> > 
> > Also we have already discussed this 2 month ago. Marek, as the u-boot
> > maintainer, can you look into enabling u-boot on qemu please?
> 
> Wouldn't it make more sense to fix the AUH so it handles U-Boot and
> similar packages correctly even without the qemu dependency ?

Note that in U-Boot we run (and run test.py on) qemu-x86 and qemux86-64
so there's no reason these days to mask U-Boot out.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

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

[Marek Vasut]

On 05/17/2018 03:04 PM, Alexander Kanavin wrote:
> On 05/17/2018 01:33 PM, Marek Vasut wrote:
>>>> Looks like AUH runs as a x86 machine, which is why it doesn't catch
>>>> u-boot.
>>>
>>> Also we have already discussed this 2 month ago. Marek, as the u-boot
>>> maintainer, can you look into enabling u-boot on qemu please?
>>
>> Wouldn't it make more sense to fix the AUH so it handles U-Boot and
>> similar packages correctly even without the qemu dependency ?
> 
> Determining the latest upstream version, performing the recipe upgrade,
> and testing that the upgraded version builds are all done by calling
> bitbake. Which of course requires that MACHINE is set to something
> specific, in this case qemux86. As u-boot is disabled there, it gets
> skipped. I could special-case u-boot, but I do think it's better to
> enable it on qemu, which would also allow better AB testing across
> architectures and during runtime (booting images) for instance.

Let's see how this works:
https://patchwork.ozlabs.org/patch/915781/

Once this gets mainline, we should then be able to enable u-boot for
qemux86/qemux86-64 . I have a patch ready for that too, but let's wait
until the U-Boot patch discussion is over.

-- 
Best regards,
Marek Vasut

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

[Alexander Kanavin]

On 05/18/2018 12:20 AM, Marek Vasut wrote:

> Let's see how this works:
> https://patchwork.ozlabs.org/patch/915781/
> 
> Once this gets mainline, we should then be able to enable u-boot for
> qemux86/qemux86-64 . I have a patch ready for that too, but let's wait
> until the U-Boot patch discussion is over.

Thanks :)

Alex