[meta-intel] Issue with ovmf license under Pyro

Wold, Saul saul.wold at intel.com
Wed Oct 4 07:15:45 PDT 2017


On Wed, 2017-10-04 at 09:00 +0200, Dominig ar Foll (Intel Open Source)
wrote:
> Hello,
> 
> I can confirm that the error is a bit random but fairly systematic on
> my system.
> I build on master from AGL. My source statement come from http://docs
> .automotivelinux.org/docs/getting_started/en/dev/reference/machines/i
> ntel.html
> 
>   source meta-agl/scripts/aglsetup.sh \
>   -m intel-corei7-64 \
>   -b build \
>   agl-devel agl-demo agl-appfw-smack agl-netboot
> 
> Mikko finding seems to be pointing to a similar issue.
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12070
> 
I need must be doing something wrong, I don't get a build with that, it
just setups up the config and spits out a list of images that can be
built.

Sau!

> Regards
> 
> Dominig
> 
> 
> Le 04/10/2017 à 07:17, Mikko Ylinen a écrit :
> > Hi, 
> > 
> > A bugzilla search for 'do_image_complete' gave me https://bugzilla.
> > yoctoproject.org/show_bug.cgi?id=12070 
> > 
> > -- Mikko 
> > 
> > 
> > On 03/10/17 21:59, Paul Eggleton wrote: 
> > > I've heard occasional reports of this issue as well and I believe
> > > it has to do 
> > > with the exact sequence of actions up to receiving the error -
> > > just setting 
> > > the configuration to be the same won't trigger it. Perhaps you
> > > need to add 
> > > something to the image and then remove it, perhaps removing the
> > > recipe 
> > > altogether? Not sure. 
> > > 
> > > Cheers, 
> > > Paul 
> > > 
> > > On Wednesday, 4 October 2017 4:38:27 AM NZDT Wold, Saul wrote: 
> > > > On Mon, 2017-10-02 at 19:41 +0200, Dominig Ar Foll wrote: 
> > > > > Hello, 
> > > > > 
> > > > > I am seeing an issue with the ovmf license in AGL,  since
> > > > > yocto has 
> > > > > moved to Pyro. 
> > > > > I can fix by deactivating it, but I do not understand why I
> > > > > see the 
> > > > > error. 
> > > > > 
> > > >  Hi Dominig, 
> > > > 
> > > > I tried to build the AGL code based on the website, I did not
> > > > see this, 
> > > > so clearly your using different branches or code. 
> > > > 
> > > > Could you point me at what your actually using please, I want
> > > > to 
> > > > confirm is this is an AGL issue or an OE-Core/meta-intel
> > > > issue. 
> > > > 
> > > > I tried with AGL master and moved meta-intel to master (from
> > > > pyro), but 
> > > > could not reproduce this issue. 
> > > > 
> > > > 
> > > > > So it will come back each time that I sync on meta-intel
> > > > > agin. 
> > > > > 
> > > > > Any help would be welcome. 
> > > > > Log and corrective patches are bellow. 
> > > > > 
> > > >  That's not really an acceptable patch for this situation. 
> > > > 
> > > > Sau! 
> > > > 
> > > > > Any help would be welcome. 
> > > > > 
> > >  
> >  
>  


More information about the meta-intel mailing list