From: "Anatol Belski" <anbelski@linux.microsoft.com>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Cc: randy.macleod@windriver.com
Subject: Current native SDK glibc compat
Date: Wed, 24 Feb 2021 12:40:02 +0100 [thread overview]
Message-ID: <4ec292a9-3723-34f2-51a5-01dd6652f651@linux.microsoft.com> (raw)
Hi,
the current master build seems to be broken with symbols unavailable
from the host glibc. The following is to see on the SDK built and
installed on the same host Ubuntu 18.04.5 having glibc 2.27:
$ . /tmp/poky-sdk-master-00/environment-setup-core2-64-poky-linux
$ ldd $(which $CC)
/tmp/poky-sdk-master-00/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found
(required by
/tmp/poky-sdk-master-00/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc)
linux-vdso.so.1 (0x00007ffdaaca2000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007feab87eb000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007feab83fa000)
/tmp/poky-sdk-master-00/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2
=> /lib64/ld-linux-x86-64.so.2 (0x00007feab8b89000)
$ objdump -T $(which $CC) | grep GLIBC_2.33
objdump: warning:
/tmp/poky-sdk-master-00/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc:
unsupported GNU_PROPERTY_TYPE (5) type: 0xc0008002
objdump: warning:
/tmp/poky-sdk-master-00/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc:
unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010001
objdump: warning:
/tmp/poky-sdk-master-00/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc:
unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010002
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.33 lstat
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.33 stat
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.33 fstat
Similar issue is observer on several other binaries consuming same
symbols. This doesn't seem a uninative issue, avoiding uninative doesn't
change this. Stable branches are fine.
I was looking through the doc but couldn't find a way to enforce a
certain symbol version usage. Please advise on a proper way to fix this.
Regards
Anatol
next reply other threads:[~2021-02-24 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 11:40 Anatol Belski [this message]
2021-02-24 12:32 ` [OE-core] Current native SDK glibc compat Richard Purdie
2021-02-24 12:56 ` Anatol Belski
2021-02-24 16:49 ` Richard Purdie
2021-02-24 20:16 ` Anatol Belski
2021-02-24 23:57 ` Richard Purdie
2021-02-25 0:23 ` Randy MacLeod
2021-02-25 19:22 ` Anatol Belski
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=4ec292a9-3723-34f2-51a5-01dd6652f651@linux.microsoft.com \
--to=anbelski@linux.microsoft.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
/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