Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Yann Dirson <yann.dirson@blade-group.com>,
	openembedded-core@lists.openembedded.org
Cc: "Andreas Müller" <schnitzeltony@gmail.com>
Subject: Re: [OE-core] Status of support for recent host glibc
Date: Fri, 5 Jun 2020 12:28:04 -0700	[thread overview]
Message-ID: <b5226094-b53d-e9b2-d23b-224bdb305dd7@gmail.com> (raw)
In-Reply-To: <CA+4=imbTdacbhmydbXLTMQm8jvNoZJfzt17Y0ZcR2gRAC7LQSg@mail.gmail.com>



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.

> 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.


  reply	other threads:[~2020-06-05 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 13:10 Status of support for recent host glibc Yann Dirson
2020-06-05 19:28 ` Khem Raj [this message]
2020-06-06  9:35   ` [OE-core] " Yann Dirson
     [not found] <1615A7E9D8CB7FC6.25101@lists.openembedded.org>
2020-06-05 13:14 ` Yann Dirson
2020-06-05 13:29   ` Paul Barker

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=b5226094-b53d-e9b2-d23b-224bdb305dd7@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=schnitzeltony@gmail.com \
    --cc=yann.dirson@blade-group.com \
    /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