Bug 11980

Summary: cmake interpreter location is set to wrong location for eSDK
Product: [Yocto Project Subprojects] eSDK Reporter: Auke-Dirk Pietersma <aukedirk>
Component: eSDKAssignee: Auke-Dirk Pietersma <aukedirk>
Status: RESOLVED WORKSFORME QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: major    
Priority: Medium+ CC: juro.bystricky
Version: 2.1.3   
Target Milestone: 2.1.4   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
steps performed to show bug none

Description Auke-Dirk Pietersma 2017-08-25 10:04:52 UTC
Created attachment 3951 [details]
steps performed to show bug

Creating and installing both eSDK and SDK with the -d option, based on the same configurations leads to different native-cmake interpreter location. Causing an error in the eSDK.

in short:

SDK correct:

auke@XX:~/workspace/beagledev$ file /home/auke/workspace/beagledev/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/cmake

/home/auke/workspace/beagledev/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/cmake: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /home/auke/workspace/beagledev/sdk/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=f2f155a8b5cfe1bada6758fe6eb491018391b0ab, stripped

eSDK incorrect:

auke@XX:~/workspace/beagledev$ which cmake
/home/auke/workspace/beagledev/esdk/sysroots/x86_64-pokysdk-linux/usr/bin/cmake

/home/auke/workspace/beagledev/esdk/sysroots/x86_64-pokysdk-linux/usr/bin/cmake: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /opt/poky/2.1.3/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=f2f155a8b5cfe1bada6758fe6eb491018391b0ab, stripped

interpreter location is /opt/poky..
resulting in a broke cmake program
Comment 1 Juro Bystricky 2017-08-31 04:51:02 UTC
seems cmake is not relocated in eSDK
Comment 2 Auke-Dirk Pietersma 2017-08-31 12:59:48 UTC
(In reply to comment #1)
> seems cmake is not relocated in eSDK

Is there something else I can do to help, provide more detailed information etc?
Comment 3 Juro Bystricky 2017-08-31 14:26:57 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > seems cmake is not relocated in eSDK
> 
> Is there something else I can do to help, provide more detailed information
> etc?

Well, if this is a relocation issue, installing the eSDK into the default location should not have this problem.
Comment 4 Juro Bystricky 2017-08-31 17:07:12 UTC
Just realized you are using "krogoth" , did you try any later distribution?
Comment 5 Juro Bystricky 2017-09-18 21:28:55 UTC
I tried to reproduce the problem (without the extra layers), but I did not suceed:

1. Build eSDK:

$ mkdir /data/master1
$ cd /data/master1
$ git clone https://git.yoctoproject.org/git/poky
$ cd poky
$ git checkout krogoth
$ source oe-init-build-env build-esdk-krogoth

local.conf (same entries as in your report):
TOOLCHAIN_HOST_TASK_append = " nativesdk-cmake"
MACHINE ?= "beaglebone"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks tools-debug ssh-server-dropbear"
IMAGE_INSTALL_append = " boost-dev"
IMAGE_INSTALL_append = " boost"
USER_CLASSES ?= "buildstats image-mklibs"
PATCHRESOLVE = "noop"
TOOLCHAIN_HOST_TASK_append = " nativesdk-boost-dev"

$ bitbake core-image-minimal -cpopulate_sdk_ext
...

$ /data/master1/poky/build-esdk-krogoth/tmp/deploy/sdk/poky-glibc-x86_64-core-image-minimal-cortexa8hf-neon-toolchain-ext-2.1.3.sh -d ~/sdk-krogoth-cortexa


$ cd ~
$ source ~/sdk-krogoth-cortexa/environment-setup-cortexa8hf-neon-poky-linux-gnueabi 


$ which cmake
/home/juro/sdk-krogoth-cortexa/sysroots/x86_64-pokysdk-linux/usr/bin/cmake

So everything behaves as it should. Please note I rebuilt everything from scratch, without any prevuious SSTATE.
Can you try to rebuild and reinstall your eSDK to see if there is a difference in behavior?
Comment 6 Juro Bystricky 2017-11-03 17:36:52 UTC
I am closing this as RESOLVED/WORKSFORME as I could not reproduce the problem
and there was no reply (for more than 6 weeks) after posting a query via NEEDINFO. 

If this problem re-appears, please re-open the bug ticket.