I am running Poky Rocko at the HEAD (just updated yesterday) and see the 
following when I attempt to build the eSDK:

sstate-control/manifest-allarch-kernel-devsrc.populate_sysroot not found?

I see this has been an issue with others as well.  It looks like Paul had a fix 
around April but then the trail went silent so I'm not sure if there was a fix 
or if that fix went into Rocko.  Anyone?

--Russ

> On July 21, 2018 at 4:42 PM Russell Peterson <bluehil...@comcast.net> wrote:
> 
> 
> No, just the standard SDK.  I was having issues building the eSDK back when 
> we used pyro and never fully figured it out… but we have since upgraded to 
> rocko.  I should revisit the eSDK and see if it works for me now or find the 
> root cause since it sounds useful.
> 
> Thanks, Khem.
> 
> —Russ
> 
> 
> > On Jul 21, 2018, at 1:34 PM, Khem Raj <raj.k...@gmail.com> wrote:
> > 
> > On Sat, Jul 21, 2018 at 6:20 AM Russell Peterson <bluehil...@comcast.net> 
> > wrote:
> >> 
> >> Hello,
> >> 
> >> I have been building some modules using the SDK for a while now.  This is 
> >> mostly for development flow purposes but we have had a few customers doing 
> >> this as well.  To get this to work we always need to run “make 
> >> silentoldconfig scripts” inside the RFS of the SDK on the build host.  
> >> Many folks forget to do this this and thus many, many questions come my 
> >> way about the SDK being broken and they can’t build their modules (not all 
> >> users are kernel experts or even intermediates… they just want to apply a 
> >> patch and quickly move on to their app).  Is there a way to do this 
> >> auto-magically during the installation of the SDK by adding some type of 
> >> scripts etc… to the recipe?  I assume it needs to be done at install time 
> >> since while the build host is x86… the exact linux distro is not known 
> >> until then (or does that matter?).
> >> 
> > 
> > are you using extensible SDK ? in that case I think do_make_scripts
> > from module-base.bbclass should be helpful
> > 
> >> —Russ
> >> 
> >> --
> >> _______________________________________________
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
> 
> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to