On Tue, 21 Jan 2020 at 09:35, Mariusz Madej <[email protected]> wrote:
>
> I use Yocto(warrior) and want to create valid extensible sdk. My problem is
> that after installation of created sdk i get:
>
> {SDK-INSTALL-DIR}/sysroots/x86_64-pokysdk-linux/usr/bin/python3: line 5:
> {SDK-INSTALL-DIR}/sysroots/x86_64-pokysdk-linux/usr/bin/python3.7.real: No
> such file or directory
>
> I installed also sdk-ext from core-image-minimal and there is no such
> problem. I started to compare differences between both installations and
> found out that my sdk has binary
> {SDK-INSTALL-DIR}/sysroots/x86_64-pokysdk-linux/usr/bin/python3.7.real and
> this binary is not relocated(wrong interpreter path). After loading sdk's
> environment, PATH variable has
> {SDK-INSTALL-DIR}/sysroots/x86_64-pokysdk-linux/usr/bin as first entry - and
> that is why devtool does not work. If i remove python3 from
> {SDK-INSTALL-DIR}/sysroots/x86_64-pokysdk-linux/usr/bin/ then devtool is
> working well. Working(relocated) python3 exists in
> {SDK-INSTALL-DIR}/buildtools/sysroots/x86_64-pokysdk-linux/usr/bin/python3 -
> the same in sdk for core-image-minimal.
>
> Can anybody tell me why i have not relocated python3 binary in
> {SDK-INSTALL-DIR}/sysroots/x86_64-pokysdk-linux/usr/bin and other sdk's dont
> have this? What kind of package it comes from? I thought it is
> nativesdk-python3 but core-image-minimal builds it also and there is no
> problem. Is there any detailed documentation about directory structure of
> installed sdk?
Hi,
I don't have the answers for your case but it looks I hit something
similar with extensible SDK on Yocto v3.0 (Zeus).
1. My distro has:
DISTRO = "eagle"
TOOLCHAIN_HOST_TASK_append = " nativesdk-u-boot-tools"
TOOLCHAIN_HOST_TASK_append += "nativesdk-cmake
2. machine:
SDKEXTPATH = "~/${@d.getVar('DISTRO')}_vf50_sdk"
3. After installing extensible SDK for my image, when I run "cmake":
$ /home/krzk/eagle_vf50_sdk/sysroots/x86_64-pokysdk-linux/usr/bin/cmake:
No such file or directory
$ file /home/krzk/eagle_vf50_sdk/sysroots/x86_64-pokysdk-linux/usr/bin/cmake
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux),
dynamically linked, interpreter /opt/eag, ....
4. The /opt/eag comes probably from:
$ bitbake -e
SDKPATH="/opt/eagle/3.0.2"
SDKPATHNATIVE="/opt/eagle/3.0.2/sysroots/x86_64-pokysdk-linux"
... but I do not set SDKPATH directly. It comes from poky defaults. I
also do not install the regular SDK.
Anyone has ideas why eSDK/sysroots/x86_64-pokysdk-linux has
non-relocated binaries with interpreter pointing to SDK (which is not
installed)?
Best regards,
Krzysztof
Best regards,
Krzysztof
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#48932): https://lists.yoctoproject.org/g/yocto/message/48932
Mute This Topic: https://lists.yoctoproject.org/mt/69952557/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
