<div dir="ltr">Hi,<br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 2, 2017 at 8:34 PM, RUSSELL PETERSON <span dir="ltr"><<a href="mailto:bluehills7@comcast.net" target="_blank">bluehills7@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>

    
<div><p>Frustrating in that I can't get the eSDK to fully build. I'm past the issue<br>with kernel-devsrc and harfbuzz... but now I see hundreds of messages like<br>below. Anyone seen this before? From what I can tell these tasks are being<br>executed out of the run queue.  Not all the messages are from cve-check but most.</p><p>Anyone seen this?</p></div></blockquote><div>Are you using devtool to work on recipes/sources? If so, try to run 'devtool reset -a' before building the eSDK. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p><br></p><p><br></p><p>ERROR: Task attr-native.do_cve_check attempted to execute unexpectedly<br>ERROR: Task binutils-native.do_cve_check attempted to execute unexpectedly<br>ERROR: Task dbus-glib.do_cve_check attempted to execute unexpectedly<br>ERROR: Task libtool-native.do_cve_check attempted to execute unexpectedly<br>ERROR: Task fixesproto.do_cve_check attempted to execute unexpectedly<br>ERROR: Task bc.do_cve_check attempted to execute unexpectedly<br>ERROR: Task lsof.do_cve_check attempted to execute unexpectedly<br>ERROR: Task python-setuptools-native.do_<wbr>cve_check attempted to execute<br>unexpectedly<br>ERROR: Task libxrandr-native.do_cve_check attempted to execute unexpectedly<br>ERROR: Task libpciaccess.do_cve_check attempted to execute unexpectedly<br>ERROR: Task xf86driproto.do_cve_check attempted to execute unexpectedly<br>ERROR: Task ncurses-native.do_cve_check attempted to execute unexpectedly</p><div><div class="h5"><p>On August 1, 2017 at 8:55 PM Russell Peterson <<a href="mailto:bluehills7@comcast.net" target="_blank">bluehills7@comcast.net</a>> wrote:</p><p>FYI: For those interested…</p><p>Just as a test/workaround I added a harfbuzz_%.bbappend file to my meta layer<br>and directly set the acpaths variable to the STAGING native directory and that<br>seems to work fine. Works for now but I will try to come up with a cleaner,<br>more generic fix.</p><p>acpaths = â€œ-I ${STAGING_DATADIR_NATIVE}/<wbr>aclocal/“</p><p>Regards,</p><p>Russell</p><blockquote><p>On Aug 1, 2017, at 5:52 PM, RUSSELL PETERSON <<a href="mailto:bluehills7@comcast.net" target="_blank">bluehills7@comcast.net</a>> wrote:</p><p>Thank you for the response, Paul. You were correct that I had the<br>TOOLCHAIN_*_TASK variables set in my machine.conf file. I put it into my<br>image bb file and things seem far more sane... although I must admit I am<br>not 100% sure why it works but I will study it a bit and figure it out.<br>Thanks for your help.</p><p>I have run into another issue while trying to generate the eSDK in that<br>there appears to be an issue with building harfbuzz. From what I can tell,<br>this appears to be an issue with the search paths for the autoreconf call.<br>The autoreconf tool is finding the pkg.m4 file in the harfbuzz m4 directory<br>FIRST and therefore not getting the one in<br>harfbuzz/1.4.1-r0/recipe-<wbr>sysroot-native/usr/share/<wbr>aclocal which indeed has<br>the correct m4_pattern_allow.</p><p>Do you think that's a bug or something with my recipe? Seems like I just<br>want to reverse the -I options... but I don't know how, exactly.</p><p>/scratch/russell/yocto-<wbr>00dc025f/work/aarch64-poky-<wbr>linux/harfbuzz/1.4.1-r0/<wbr>recipe-sysroot-native/usr/bin/<wbr>autoconf<br>--include=/scratch/russell/<wbr>yocto-00dc025f/work/aarch64-<wbr>poky-linux/harfbuzz/1.4.1-r0/<wbr>harfbuzz-1.4.1/m4/<br>--include=/scratch/russell/<wbr>yocto-00dc025f/work/aarch64-<wbr>poky-linux/harfbuzz/1.4.1-r0/<wbr>recipe-sysroot-native/usr/<wbr>share/aclocal/<br>--force</p><p>../../../autoconf-2.69/lib/<wbr>autoconf/specific.m4:368:<br>AC_USE_SYSTEM_EXTENSIONS is expanded from...<br>| <a href="http://configure.ac:22" target="_blank">configure.ac:22</a>: the top level<br>| configure:18902: error: possibly undefined macro: PKG_CONFIG_SYSROOT_DIR<br>| If this token and others are legitimate, please use m4_pattern_allow.<br>| See the Autoconf documentation.<br>| autoreconf:<br>/scratch/russell/yocto-<wbr>00dc025f/work/aarch64-poky-<wbr>linux/harfbuzz/1.4.1-r0/<wbr>recipe-sysroot-native/usr/bin/<wbr>autoconf<br>failed with exit status: 1<br>| ERROR: Function failed: do_configure (log file is located at<br>/scratch/russell/yocto-<wbr>00dc025f/work/aarch64-poky-<wbr>linux/harfbuzz/1.4.1-r0/temp/<wbr>log.do_configure.14956)</p><blockquote><p>On July 31, 2017 at 9:50 AM Paul Eggleton <<a href="mailto:paul.eggleton@linux.intel.com" target="_blank">paul.eggleton@linux.intel.com</a><wbr>><br>wrote:</p><p>Hi Russell,</p><p>It looks to me like you have added kernel-devsrc to the TOOLCHAIN_*_TASK<br>variable at the global level, which you really don't want to do if you're<br>going to be building buildtools-tarball (which eSDK will build as a<br>dependency). I'd suggest moving that setting to your image recipe.</p><p>Cheers,<br>Paul</p><p>On Sunday, 30 July 2017 4:22:24 PM CEST Russell Peterson wrote:</p><blockquote><p>Hello, all.</p><p>I’m trying to build the eSDK for my platform and I just can’t figure out<br>why dnf can’t find kernel-devsrc. It’s there, I added it. The â€œnormal<br>SDK” uses it and builds fine. Just no luck with the eSDK.<br>Any help out there? Poky is pyro. aarch64 SoC target platform with an<br>x86 build host (CentOS 7.3). Basically I just bitbake -c<br>do_populate_sdk_ext core-image-full. I do have a linux kernel recipe<br>that pulls the kernel from the standard <a href="http://kernel.org" target="_blank">kernel.org</a> <<a href="http://kernel.org/" target="_blank">http://kernel.org/</a>><br>repo.</p><p>ERROR: buildtools-tarball-1.0-r0 do_populate_sdk: Could not invoke dnf.<br>Command<br>'/scratch/russell/yocto-<wbr>00dc025f/work/x86_64-<wbr>nativesdk-pokysdk-linux/<wbr>buildtools-tarball/1.0-r0/<wbr>recipe-sysroot-native/usr/bin/<wbr>dnf<br>-y -c<br>/scratch/russell/yocto-<wbr>00dc025f/work/x86_64-<wbr>nativesdk-pokysdk-linux/<wbr>buildtools-tarball/1.0-r0/sdk/<wbr>image/opt/poky/2.3.1/sysroots/<wbr>none/etc/dnf/dnf.conf<br>--setopt=reposdir=/scratch/<wbr>russell/yocto-00dc025f/work/<wbr>x86_64-nativesdk-pokysdk-<wbr>linux/buildtools-tarball/1.0-<wbr>r0/sdk/image/opt/poky/2.3.1/<wbr>sysroots/none/etc/yum.repos.d<br>--repofrompath=oe-repo,/<wbr>scratch/russell/yocto-<wbr>00dc025f/work/x86_64-<wbr>nativesdk-pokysdk-linux/<wbr>buildtools-tarball/1.0-r0/oe-<wbr>rootfs-repo<br>--installroot=/scratch/<wbr>russell/yocto-00dc025f/work/<wbr>x86_64-nativesdk-pokysdk-<wbr>linux/buildtools-tarball/1.0-<wbr>r0/sdk/image/opt/poky/2.3.1/<wbr>sysroots/none<br>--setopt=logdir=/scratch/<wbr>russell/yocto-00dc025f/work/<wbr>x86_64-nativesdk-pokysdk-<wbr>linux/buildtools-tarball/1.0-<wbr>r0/temp<br>--nogpgcheck install kernel-devsrc' returned 1:<br>Added oe-repo repo from<br>file:///scratch/russell/yocto-<wbr>00dc025f/work/x86_64-<wbr>nativesdk-pokysdk-linux/<wbr>buildtools-tarball/1.0-r0/oe-<wbr>rootfs-repo<br><file:///scratch/russell/<wbr>yocto-00dc025f/work/x86_64-<wbr>nativesdk-pokysdk-linux/<wbr>buildtools-tarball/1.0-r0/oe-<wbr>rootfs-repo><br>Last metadata expiration check: 0:00:01 ago on Sun Jul 30 01:38:48 2017<br>UTC.<br>No package kernel-devsrc available.<br>Error: Unable to find a match</p><p>ERROR: buildtools-tarball-1.0-r0 do_populate_sdk: Function failed:<br>do_populate_sdk<br>ERROR: Logfile of failure stored in:<br>/scratch/russell/yocto-<wbr>00dc025f/work/x86_64-<wbr>nativesdk-pokysdk-linux/<wbr>buildtools-tarball/1.0-r0/<wbr>temp/log.do_populate_sdk.4836<br>ERROR: Task<br>(/labhome/russell/src/bf/poky/<wbr>meta/recipes-core/meta/<wbr>buildtools-tarball.bb:do_<wbr>populate_sdk)<br>failed with exit code '1'</p></blockquote><p>--</p><p>Paul Eggleton</p><p>Intel Open Source Technology Centre<br>--</p><p>______________________________<wbr>_________________<br>yocto mailing list<br><a href="mailto:yocto@yoctoproject.org" target="_blank">yocto@yoctoproject.org</a><br><a href="https://lists.yoctoproject.org/listinfo/yocto" target="_blank">https://lists.yoctoproject.<wbr>org/listinfo/yocto</a></p></blockquote></blockquote></div></div></div>
 <br>--<br>
______________________________<wbr>_________________<br>
yocto mailing list<br>
<a href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><br>
<a href="https://lists.yoctoproject.org/listinfo/yocto" rel="noreferrer" target="_blank">https://lists.yoctoproject.<wbr>org/listinfo/yocto</a><br>
<br></blockquote></div><br></div></div>