On Sun, 2022-04-03 at 09:12 +0200, Federico Pellegrin wrote:
I've been playing around building a Yocto imagine based on kirkstone/master on
the just released Fedora 36 beta test image. (just to give a few bits more
details: builds a MX8X image, works perfectly fine with Fedora 34 and 35 since
quite some time)
The first and most obvious thing I've found out is that it is based on a newer
version of glibcxx (3.4.30) when the very latest uninative available (as far
as I could see, apologies if I'm wrong) is on 3.4.29, so at some point this
will break the build (when pzstd is called).
Of course for the time being I just disabled uninative and the build is going
on (will report of course should I find something else). I'm not sure (still
checking this) if that should have happened automatically, but there was
actually no warning in that sense (maybe because is GLIBCXX and not GLIBC
But the question is: should I try to contribute that tarball (I will search
for details, but if there is any good reference more than welcome!) or is it
something that is likely done by the core team?
Of course FC36 is still a test distro so there is no surprise it broke, but as
we are close to Kirkstone release and possibly other distros will get the same
upgrade, I guess it could be great if we may fix this before that deadline.
Thanks for reporting it. I think to generate the newer version we need gcc 12
which is still in pre-release. We generate the uninative tarball using our own
builds on the autobuilder so until we have gcc 12 recipes there, we can't
Once gcc 12 is out, we will release a new uninative (assuming we can update our
I'd like to think the checks in uninative would have noticed the mismatch, we do
have some code there to detect libc version but perhaps not the CXX pieces so
I'd welcome help in adding something for that.