Re: [OE-core] Status of support for recent host glibc

From: "Yann Dirson" <yann.dirson@blade-group.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	"Andreas Müller" <schnitzeltony@gmail.com>
Subject: Re: [OE-core] Status of support for recent host glibc
Date: Sat, 6 Jun 2020 11:35:16 +0200	[thread overview]
Message-ID: <CA+4=imYx=qB5bV8Y3L7zZUSqUoc58nzv9ZJyfLbaJ3s-KYO_sg@mail.gmail.com> (raw)
In-Reply-To: <b5226094-b53d-e9b2-d23b-224bdb305dd7@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2438 bytes --]

Le ven. 5 juin 2020 à 21:28, Khem Raj <raj.khem@gmail.com> a écrit :

>
>
> On 6/5/20 6:10 AM, Yann Dirson wrote:
> > I just got hit by the following dunfell build issue on my debian/testing
> > dev box:
> >
> >   argp-fmtstream.c:(.text+0x4ca): undefined reference to `_IO_fwide'
> >
>  /home/yann/yocto/meta-blade/meta-shadow-os/build-boxv2/tmp/hosttools/ld:
> argp-fmtstream.c:(.text+0x51d): undefined reference to `_IO_fwide'
> >
>  /home/yann/yocto/meta-blade/meta-shadow-os/build-boxv2/tmp/hosttools/ld:
> argp-help.o: in function `argp_failure':
> >   argp-help.c:(.text+0x1fb1): undefined reference to `_IO_fwide'
> >   collect2: error: ld returned 1 exit status
> >   make: *** [Makefile:60: localedef] Error 1
> >
> > After some digging I found
> > https://patchwork.openembedded.org/series/20136 whose patch 4
> > addresses this very problem.
> >
>
> Please send a backport request if its not already done so and Cc Steve
> Sakoman ( dunfell maintainer ), also  check the supported hosts list for
> dunfell
>
>
> https://www.yoctoproject.org/docs/3.1/ref-manual/ref-manual.html#detailed-supported-distros
>
> this case is not seen on commonly supported distros hence no request to
> backport perhaps. Debian testing is rolling distibution and its hard to
> support time based releases on top of rolling host distributions.
>

Well, since those days I'm working on migrating away from sumo, I'll avoid
diverting
other's efforts there, since building in a chroot is pretty fine.

> > I could not find any discussion about those patches (it's hard to be
> > sure though, I found the
> > new mail archive quite impractical).
> >
> > Are there any reasons why this 2019-09 series is still NEW ?
>
> I know its confusing but
> For OE-core and bitbake too, patchwork is not primary tool for
> cherry-picking patches from mailing list, its email based, since its
> primarily driven by maintainer's convenience more than anything else. so
> dont read into status of the patchwork series status.
>
>
OK. But then it looks like the mail archive ought to make it easier to
navigate threads - I spent quite
some time trying to figure out if there had been any followup to this
series, and I'm still usure of the
answer.  It seems quite surprising there would be no thread view in this
software ?

-- 
Yann Dirson <yann@blade-group.com>
Blade / Shadow -- http://shadow.tech

[-- Attachment #2: Type: text/html, Size: 3563 bytes --]