From: "Robert" <pwr@iae.nl>
To: yocto@yoctoproject.org
Subject: poky-dunfell-23.0.2: WARNING: Your host glibc verson (2.32) is newer than that in uninative (2.31). Disabling uninative so that sstate is not corrupted.
Date: Sun, 27 Sep 2020 23:02:28 +0200 [thread overview]
Message-ID: <3293b1b2-36fe-3bec-e0b7-07cd228fc4c7@iae.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
Hello list,
The warning in the subject has turned into an error.
I'm building a Yocto project based on poky-dunfell-23.0.2
I get this error:
ERROR: dpkg-native-1.19.7-r0 do_compile: oe_runmake failed
| ../../../dpkg-1.19.7/lib/compat/strsignal.c: In function ‘test_strsignal’:
| ../../../dpkg-1.19.7/lib/compat/strsignal.c:71:10: error:
‘sys_siglist’ undeclared (first use in this function)
| 71 | return sys_siglist[s];
I found the reason for this error:
Release notes of glibc 2.32:
https://sourceware.org/pipermail/libc-announce/2020/000029.html
* The deprecated arrays *sys_siglist*, _sys_siglist, and sys_sigabbrev
are no longer available to newly linked binaries, and their declarations
have been *removed* from <string.h>. They are exported solely as
compatibility symbols to support old binaries. All programs should use
strsignal instead.
To solve it I could downgrade the glibc library version of my system
(general consensus on forums is that, that is a bad idea).
Other option:
In the master branch I find a recipe for dpkg 1.20.5, can I simply
upgrade the dpkg version (1.19.7) in the dunfell release with the master
branch version (1.20.5)?
Could it break anything and how do I know it will solve my problem?
Other then try it.
Or is there another solution?
uname -rmo
Linux 5.4.64-1-MANJARO x86_64 GNU/Linux
Thanks,
Robert.
[-- Attachment #2: Type: text/html, Size: 2018 bytes --]
next reply other threads:[~2020-09-27 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 21:02 Robert [this message]
2020-09-28 2:07 ` [yocto] poky-dunfell-23.0.2: WARNING: Your host glibc verson (2.32) is newer than that in uninative (2.31). Disabling uninative so that sstate is not corrupted Martin Jansa
2020-09-28 8:34 ` Robert
2020-09-28 11:45 ` Richard Purdie
2020-09-28 16:53 ` Martin Jansa
2020-09-28 17:00 ` Robert
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=3293b1b2-36fe-3bec-e0b7-07cd228fc4c7@iae.nl \
--to=pwr@iae.nl \
--cc=yocto@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