public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Sundeep KOKKONDA <sundeep.kokkonda@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [kirkstone] glibc : stable 2.35 branch updates
Date: Thu, 4 Aug 2022 13:57:56 +0200	[thread overview]
Message-ID: <Yuu0RAEKrQp7uD/M@jama> (raw)
In-Reply-To: <19859.1659612044516984045@lists.openembedded.org>

On Thu, Aug 04, 2022 at 04:20:44AM -0700, Sundeep KOKKONDA wrote:
> Is there a fix available for this issue and was it taken to glibc branches? I checked glibc 2.35 branch now could not see any new commits available.
> If there is any fix/workaround required then it should be patched in ' meta/recipes-core/glibc/ ' OR if it is a bug in glibc then it should be corrected by glibc. It seems the mentioned issue is still on-going and no fix is available yet.

Then maybe we should hold on more "stable" updates for kirkstone, before
the DEBUG_BUILD regression from the previous upgrade is fixed? The
regression tests are great, but they don't help to detect issues like
the DEBUG_BUILD.

This change also seems to target kirkstone directly without being tested
in master first. I know Khem has a change for 2.36 glibc for master, but
maybe merging this update in master first (and resolving the DEBUG_BUILD
issue even with that revert I've sent earlier) could be merged before
that.


  parent reply	other threads:[~2022-08-04 11:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  4:11 [kirkstone] glibc : stable 2.35 branch updates Sundeep KOKKONDA
2022-08-04  4:18 ` Sundeep KOKKONDA
2022-08-04  9:52   ` [OE-core] " Martin Jansa
2022-08-04 11:20     ` Sundeep KOKKONDA
2022-08-04 11:22       ` [OE-core] " Khem Raj
2022-08-04 11:57       ` Martin Jansa [this message]
2022-08-04 14:25         ` Steve Sakoman
  -- strict thread matches above, loose matches on Subject: below --
2022-09-15 11:14 Sundeep KOKKONDA
2022-09-15 11:20 ` Sundeep KOKKONDA
2022-09-15 14:28   ` [OE-core] " Khem Raj
2022-09-16  5:48     ` Sundeep KOKKONDA
2022-10-25  9:18 [kirkstone] glibc: " Yash Shinde
2022-10-27 17:20 ` [OE-core] " Randy MacLeod
2022-10-27 17:42   ` Steve Sakoman
2022-10-27 18:32   ` Yash Shinde
2022-10-27 19:40     ` Steve Sakoman

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=Yuu0RAEKrQp7uD/M@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sundeep.kokkonda@gmail.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