Re: [yocto] extensible SDK build failure

Hi Russell, I'm also hitting the same "unexpected" errors for my linux-yocto-xxx.bb recipe/tasks while building extensible SDK for my platform. How did it work for you? Warm Regards, Priyanshu Sharma -- ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] extensible SDK build failure

Thanks, Paul. That helped, however, I still see some of the same “unexpected” errors for perf tasks as well as my virtual/kernel tasks. I presume SDK_INHERIT_BLACKLIST excludes the use of the class for the SDK… but I am unclear as to why I see these errors with my linux-yocto-xxx.bb

Re: [yocto] extensible SDK build failure

Hi Russell, On Wednesday, 2 August 2017 8:34:11 PM CEST RUSSELL PETERSON wrote: > Frustrating in that I can't get the eSDK to fully build. I'm past the issue > with kernel-devsrc and harfbuzz... but now I see hundreds of messages like > below. Anyone seen this before? From what I can tell these

Re: [yocto] extensible SDK build failure

Thanks for the help but, no. I’m just trying to build the eSDK via the normal bitbake process. Russell > On Aug 4, 2017, at 11:52 AM, Andrea Galbusera wrote: > > Hi, > > On Wed, Aug 2, 2017 at 8:34 PM, RUSSELL PETERSON

Re: [yocto] extensible SDK build failure

Hi, On Wed, Aug 2, 2017 at 8:34 PM, RUSSELL PETERSON wrote: > Frustrating in that I can't get the eSDK to fully build. I'm past the issue > with kernel-devsrc and harfbuzz... but now I see hundreds of messages like > below. Anyone seen this before? From what I can tell

Re: [yocto] extensible SDK build failure

Frustrating in that I can't get the eSDK to fully build. I'm past the issue with kernel-devsrc and harfbuzz... but now I see hundreds of messages like below. Anyone seen this before? From what I can tell these tasks are being executed out of the run queue. Not all the messages are from cve-check

Re: [yocto] extensible SDK build failure

FYI: For those interested… Just as a test/workaround I added a harfbuzz_%.bbappend file to my meta layer and directly set the acpaths variable to the STAGING native directory and that seems to work fine. Works for now but I will try to come up with a cleaner, more generic fix. acpaths = “-I

Re: [yocto] extensible SDK build failure

Thank you for the response, Paul. You were correct that I had the TOOLCHAIN_*_TASK variables set in my machine.conf file. I put it into my image bb file and things seem far more sane... although I must admit I am not 100% sure why it works but I will study it a bit and figure it out. Thanks for

Re: [yocto] extensible SDK build failure

Hi Russell, It looks to me like you have added kernel-devsrc to the TOOLCHAIN_*_TASK variable at the global level, which you really don't want to do if you're going to be building buildtools-tarball (which eSDK will build as a dependency). I'd suggest moving that setting to your image recipe.

[yocto] extensible SDK build failure

Hello, all. I’m trying to build the eSDK for my platform and I just can’t figure out why dnf can’t find kernel-devsrc. It’s there, I added it. The “normal SDK” uses it and builds fine. Just no luck with the eSDK. Any help out there? Poky is pyro. aarch64 SoC target platform with an x86