Bug 13694

Summary: Installing eSDK fails
Product: [Yocto Project Subprojects] eSDK Reporter: Lars Andersson <larsand>
Component: eSDKAssignee: akuster <akuster808>
Status: CLOSED WORKSFORME QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: Medium CC: akuster, richard.purdie
Version: 2.7.2   
Target Milestone: 2.7.3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
Installation Log none

Description Lars Andersson 2019-12-09 10:40:05 UTC
Created attachment 4596 [details]
Installation Log

I've been trying to install the extensible SDK using a number of Yocto Releases (Sumo, Thud, Warrior) but installing the eSDK always fails with a large number of error messages along the lines of:

"Task cmake-native.do_configure attempted to execute unexpectedly."

Please see the attached SDK installation for full details.

I'm using the IMX version of Yocto Warrior, installed using:

~/bin/repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-warrior -m imx-4.19.35-1.1.0.xml

Image and eSDK were built using the command:

$ bitbake fsl-image-qt5-validation-imx -c populate_sdk_ext


Any idea what could be wrong?
Comment 1 Lars Andersson 2019-12-09 13:05:48 UTC
Btw, my host is running Ubuntu 18.04 (x86_64), and I'm using x86_64-buildtools-nativesdk-standalone-2.7.2.sh as buildtools.
Comment 2 Richard Purdie 2019-12-12 15:58:28 UTC
We test eSDK with OE-Core. Could you test this without the meta-freescale layer using one of the machines from OE-Core to confirm where the issue is?

We strngly suspect the meta-freescale layer isn't tested with eSDK and there is something in there causing this issue. If that is the case it would need to be raised with the freescale layer maintainers.
Comment 3 Armin Kuster 2020-02-03 02:04:27 UTC
(In reply to comment #2)
> We test eSDK with OE-Core. Could you test this without the meta-freescale
> layer using one of the machines from OE-Core to confirm where the issue is?
> 
> We strngly suspect the meta-freescale layer isn't tested with eSDK and there
> is something in there causing this issue. If that is the case it would need
> to be raised with the freescale layer maintainers

Since I have not heard back on this, I am marking it as "WorksForMe"
Comment 4 Armin Kuster 2020-02-03 02:04:41 UTC
closed