uninative: Upgrade to 3.9 to include glibc 2.37

From: Michael Halstead <mhalstead@linuxfoundation.org>

Update uninative to work with the new glibc 2.37.

Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

On Tue, Feb 7, 2023 at 10:54 PM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> From: Michael Halstead <mhalstead@linuxfoundation.org>
>
> Update uninative to work with the new glibc 2.37.
>


> Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
>  meta/conf/distro/include/yocto-uninative.inc | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/meta/conf/distro/include/yocto-uninative.inc
> b/meta/conf/distro/include/yocto-uninative.inc
> index 51c0cdee438..8a5cab5360d 100644
> --- a/meta/conf/distro/include/yocto-uninative.inc
> +++ b/meta/conf/distro/include/yocto-uninative.inc
> @@ -6,10 +6,10 @@
>  # to the distro running on the build machine.
>  #
>
> -UNINATIVE_MAXGLIBCVERSION = "2.36"
> -UNINATIVE_VERSION = "3.8.1"
> +UNINATIVE_MAXGLIBCVERSION = "2.37"
> +UNINATIVE_VERSION = "3.9"
>

Was there some dependency on other changes to consider this for backport to
langdale (which already has the libgcc change with 3.8.1) and then
kirkstone (needs both update to 3.8.1 and then this).

I'll start using it for my ubuntu-23.10 builds (with glibc 2.37) and ask
for backport later if there is no reply on this.

Cheers,

On Tue, 2023-03-28 at 22:13 +0200, Martin Jansa wrote:
> On Tue, Feb 7, 2023 at 10:54 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > From: Michael Halstead <mhalstead@linuxfoundation.org>
> > 
> > Update uninative to work with the new glibc 2.37.
> > 
> 
> 
> > 
> > Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> >  meta/conf/distro/include/yocto-uninative.inc | 10 +++++-----
> >  1 file changed, 5 insertions(+), 5 deletions(-)
> > 
> > diff --git a/meta/conf/distro/include/yocto-uninative.inc
> > b/meta/conf/distro/include/yocto-uninative.inc
> > index 51c0cdee438..8a5cab5360d 100644
> > --- a/meta/conf/distro/include/yocto-uninative.inc
> > +++ b/meta/conf/distro/include/yocto-uninative.inc
> > @@ -6,10 +6,10 @@
> >  # to the distro running on the build machine.
> >  #
> > 
> > -UNINATIVE_MAXGLIBCVERSION = "2.36"
> > -UNINATIVE_VERSION = "3.8.1"
> > +UNINATIVE_MAXGLIBCVERSION = "2.37"
> > +UNINATIVE_VERSION = "3.9"
> > 
> 
> 
> Was there some dependency on other changes to consider this for
> backport to langdale (which already has the libgcc change with 3.8.1)
> and then kirkstone (needs both update to 3.8.1 and then this).
> 
> I'll start using it for my ubuntu-23.10 builds (with glibc 2.37) and
> ask for backport later if there is no reply on this.

Uninative should generally be safe for backporting.

Cheers,

Richard

Over night I got one failure in kirkstone with new uninative:

Exception: subprocess.CalledProcessError: Command '('patchelf-uninative',
'--set-interpreter',
'TOPDIR/BUILD/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2',
'TOPDIR/BUILD/work/x86_64-linux/3gpt/fakes/sstate-build-populate_sysroot/recipe-sysroot-native/usr/bin/makePr0n')'
returned non-zero exit status 1.

Subprocess output:
patchelf: open: Permission denied

After discussing with RP on #yocto he mentioned patchelf change related to
this and that's:
https://git.openembedded.org/openembedded-core/commit/?id=728775c87a7e35a03408675ce1c7a8cd061b2fda
which is already in langdale and does apply for kirkstone.

I've backported this for my kirkstone builds and will send formal backport
request for all 4 changes after a bit more testing (even safe things tend
to break if you build a lot of weird stuff).

Regards,

On Tue, Mar 28, 2023 at 10:33 PM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Tue, 2023-03-28 at 22:13 +0200, Martin Jansa wrote:
> > On Tue, Feb 7, 2023 at 10:54 PM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > > From: Michael Halstead <mhalstead@linuxfoundation.org>
> > >
> > > Update uninative to work with the new glibc 2.37.
> > >
> >
> >
> > >
> > > Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
> > > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > ---
> > >  meta/conf/distro/include/yocto-uninative.inc | 10 +++++-----
> > >  1 file changed, 5 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/meta/conf/distro/include/yocto-uninative.inc
> > > b/meta/conf/distro/include/yocto-uninative.inc
> > > index 51c0cdee438..8a5cab5360d 100644
> > > --- a/meta/conf/distro/include/yocto-uninative.inc
> > > +++ b/meta/conf/distro/include/yocto-uninative.inc
> > > @@ -6,10 +6,10 @@
> > >  # to the distro running on the build machine.
> > >  #
> > >
> > > -UNINATIVE_MAXGLIBCVERSION = "2.36"
> > > -UNINATIVE_VERSION = "3.8.1"
> > > +UNINATIVE_MAXGLIBCVERSION = "2.37"
> > > +UNINATIVE_VERSION = "3.9"
> > >
> >
> >
> > Was there some dependency on other changes to consider this for
> > backport to langdale (which already has the libgcc change with 3.8.1)
> > and then kirkstone (needs both update to 3.8.1 and then this).
> >
> > I'll start using it for my ubuntu-23.10 builds (with glibc 2.37) and
> > ask for backport later if there is no reply on this.
>
> Uninative should generally be safe for backporting.
>
> Cheers,
>
> Richard
>