Re: [poky] Poky calls host pzstd with uninative's libstdc++.so.6 instead of the host library

Tamara Schmitz <[email protected]>
Newsgroups org.yoctoproject.lists.poky
Organization kernel concepts GmbH
Message-ID <[email protected]>
On Wed, 2024-09-04 at 10:41 +0100, Richard Purdie wrote:
> A key piece of information is which version of poky are you trying to
> build?
> 

The Vendor BSP specifies branch scarthgap commit
02eacd385eca7aa9cf25aaaa61427aa9c126e0bc which is between the yocto-5.0
and the yocto-5.0.1 release tag which is from May. Yeah could use an
update.


> uninative changes the loader of executables to use the loader from
> uninative rather than the host system. It does this so that binaries
> built on a newer distro can work on an older one.
> 
> The cost of doing that is that you need to use a uninative that
> matches
> or is greater than the host system.

Wouldn't it be great if Poky could distinct between host binaries and
its own binaries?

> 
> I'd therefore suggest bumping the version of uninative in the
> metadata
> you're using. Whilst it isn't a supported version, chances are it
> will
> probably work if you do that.
> 

Will try that.

> 
> The bug is that you're using an unsupported distro without making the
> modifications needed to support it. You can disable uninative, or you
> can switch to a newer uninative release, or switch to a version of
> the
> system which has fedora40 support.
> 
> There will be other issues with fedora 40 as some things won't build
> correctly due to the newer gcc version on f40 too.
> 

Yeah, I am fine with taking a look at those. The warning did warn me
after all ;)


Regards

Tamara
signature.asc (application/pgp-signature, 273 B)
-----BEGIN PGP SIGNATURE-----

iJcEABYKAD8WIQQ6pYmxf78Oo/3+lugLvc+XfT8YVQUCZtgwDiEcdGFtYXJhLnNj
aG1pdHpAa2VybmVsY29uY2VwdHMuZGUACgkQC73Pl30/GFUJawD/YE3IZOxa84N+
g/AShvkc0JcQyBnXUQ/GMTJPFKk0AWMA/ArxsHa7H4j5GGRK1Lt6BXrjBlg+c8va
sL1AXAJB8voB
=VhY0
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.