From: "Nicolas Wirth" <nicolas.wirth@speedgoat.ch>
To: poky@lists.yoctoproject.org
Subject: Issue with Dynamic Linker and Python Dependency in Yocto SDK Setup
Date: Fri, 21 Jun 2024 04:49:16 -0700 [thread overview]
Message-ID: <6txm.1718970556825135447.eRWi@lists.yoctoproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
Hi everyone,
I'm currently facing an issue while setting up a Yocto SDK environment using the bitbake my-image -c populate_sdk command. The SDK needs to be deployed on a machine that has no existing installations and lacks Python. To work around this, I've modified SDK_PACKAGING_FUNC to "do_compile" instead of "create_shar" to directly obtain the source files.
However, when I try to set up the environment using the generated SDK, I encounter the following error related to the dynamic linker:
. /yocto-sdk/june-21-linux-x86/environment-setup-core2-64-poky-linux
$CC : no such file or directory: x86_64-poky-linux-gcc ...
which $CC : x86_64-poky-linux-gcc not found
ldd /yocto-sdk/june-21-linux-x86/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc linux-vdso.so.1 (0x00007ffca9731000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007faf662c7000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007faf660e6000) /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007faf663af000)
file /yocto-sdk/june-21-linux-x86/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc /yocto-sdk/june-21-linux-x86/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2, BuildID[sha1]=d5ac41fb03fc89ca348393a6e8734b6fc93ee561, for GNU/Linux 3.2.0, stripped
Since I don't have Python installed, I am unable to run relocate_sdk.py. Could someone please advise on how to resolve this issue or suggest alternative approaches to correctly set up the Yocto SDK environment without Python?
Best regards, Nicolas
[-- Attachment #2: Type: text/html, Size: 2376 bytes --]
next reply other threads:[~2024-06-21 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 11:49 Nicolas Wirth [this message]
2024-06-21 13:23 ` [poky] Issue with Dynamic Linker and Python Dependency in Yocto SDK Setup Ross Burton
2024-06-24 7:17 ` Nicolas Wirth
2024-06-24 7:19 ` [poky] " Alexander Kanavin
2024-06-24 7:24 ` Nicolas Wirth
[not found] ` <Groupsio.1.6942.1719213477427571414@lists.yoctoproject.org>
2024-06-24 17:03 ` [poky] " Khem Raj
2024-06-25 6:46 ` Nicolas Wirth
2024-06-25 8:10 ` [poky] " Richard Purdie
2024-06-26 11:39 ` Nicolas Wirth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6txm.1718970556825135447.eRWi@lists.yoctoproject.org \
--to=nicolas.wirth@speedgoat.ch \
--cc=poky@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox