On Wed, 02 Nov 2016 07:25:13 Gary Thomas wrote: > I've tested your patches for this (from the OE-core mailing list) > and I can now build and use the eSDK for my board :-)
Great! > I do have a couple observations/questions: > > * I added my missing tool with this line in my local.conf > TOOLCHAIN_HOST_TASK_append = " nativesdk-ti-cgt-pru" > Why did this cause many of the nativesdk tools to have to be rebuilt? So just FYI this will only work for the standard SDK, it's not the right way to add these tools for the eSDK - in fact it may break the eSDK due to bringing things into the native sysroot that shouldn't be there. At the moment I think the only way to properly add this to the eSDK is to do this: SDK_TARGETS += "ti-cgt-pru-native:do_populate_sysroot" We don't document this, and it's a little awkward in any case. I'll work on it. > * When I built 'nativesdk-ti-cgt-pru', I got a number of scary looking > errors - here are a few: ERROR: nativesdk-ti-cgt-pru-2.1.1-r0 do_configure: > Taskhash mismatch eb0229a8c364c4c399fc2e84f4dfaf91 versus > b5d16aa43836f3832200af39aba5b796 for > virtual:nativesdk:/local/poky-cutting-edge/meta-ti/recipes-ti/devtools/ti-cg > t-pru_2.1.1.bb.do_configure ERROR: Taskhash mismatch > eb0229a8c364c4c399fc2e84f4dfaf91 versus b5d16aa43836f3832200af39aba5b796 > for > virtual:nativesdk:/local/poky-cutting-edge/meta-ti/recipes-ti/devtools/ti-c > gt-pru_2.1.1.bb.do_configure ERROR: nativesdk-ti-cgt-pru-2.1.1-r0 > do_compile: Taskhash mismatch bc0d6bb3a62f58875962d4ccf1b60dd9 versus > 9e207a5a6aa53512135b5ea3a0610bf3 for > virtual:nativesdk:/local/poky-cutting-edge/meta-ti/recipes-ti/devtools/ti-cg > t-pru_2.1.1.bb.do_compile Where did you build this? Just in your normal build? This kind of error indicates that a variable value is changing while bitbake is running - often this is caused by date/time values in variables. Looking in meta-ti I can't see anything that would cause this though. Was it only showing up for nativesdk-ti-cgt-pru ? > * When I installed the eSDK on a machine other than where I > built it, I also got a lot (865) of messages like these: > > WARNING: The quilt-native:do_configure sig is computed to be > 315b89079a159e1d4e43d3199c487bdb, but the sig is locked to > a9909bdcc4c81106eb42c21bb0d760fc in SIGGEN_LOCKEDSIGS_t-x86-64 > The quilt-native:do_compile sig is computed to be > be128011cc1f47157898f513dc4e9bbb, but the sig is locked to > fa83446de41fe9e7c2c49c2745438a8d in SIGGEN_LOCKEDSIGS_t-x86-64 > The quilt-native:do_install sig is computed to be > 85c8be820a93b84901dd7528eb61840e, but the sig is locked to > 6caa366055ef06147ef64cbe7d83c608 in SIGGEN_LOCKEDSIGS_t-x86-64 > The quilt-native:do_populate_sysroot sig is computed to be > 5b0f52254aa8548fa406b806dae000cb, but the sig is locked to > d3cf7e526716d0286ce596c44c6b9936 in SIGGEN_LOCKEDSIGS_t-x86-64 > The glibc:do_patch sig is computed to be 373272e62465460928320aa7643f9916, > but the sig is locked to 712620a3943887e11d9730013d1e07f0 in > SIGGEN_LOCKEDSIGS_t-armv7ahf-neon Right. Are you using uninative? If not, you probably should (and I just sent a patch to disable building the eSDK without it). > All that said, it is now working for me, time to learn to use it! > Thanks for your help. Feel free to add my Acked-by or Signed-off-by > to your patches if you wish. > > Acked-by: Gary Thomas <g...@mlbassoc.com> > Signed-off-by: Gary Thomas <g...@mlbassoc.com> Thanks! Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
