public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: openembedded-core@lists.openembedded.org, "Kokkonda,
	Sundeep" <Sundeep.Kokkonda@windriver.com>
Cc: Khem Raj <raj.khem@gmail.com>,
	"steve@sakoman.com" <steve@sakoman.com>,
	Sundeep KOKKONDA <sundeep.kokkonda@gmail.com>
Subject: Re: [OE-core] [kirkstone] binutils: stable 2.38 branch updates
Date: Tue, 13 Sep 2022 14:42:09 -0400	[thread overview]
Message-ID: <7cd419c6-f3fc-6ebe-8dee-ee969d26e88a@windriver.com> (raw)
In-Reply-To: <d96f949e-99f9-82e9-088e-d351327adba9@gmail.com>

On 2022-09-13 12:59, Khem Raj wrote:
> On 9/13/22 2:43 AM, Sundeep KOKKONDA wrote:
>> Hello,
>> I am planning to take the gcc, glibc & binutils updates to Kirkstone. 
>> I found only the glibc-2.35 branch is having a few updates (given 
>> below).
>> /f8ad66a4ca nscd: Fix netlink cache invalidation if epoll is used [BZ 
>> #29415]/
>> /9e960717e1 Apply asm redirections in wchar.h before first use/
>> /577c2fc7f3 elf: Call __libc_early_init for reused namespaces (bug 
>> 29528)/
>> /83f1d9851e NEWS: Add entry for bug 28846/
>> /cbd8685e82 socket: Check lengths before advancing pointer in 
>> CMSG_NXTHDR/
>> /4bafc4001d alpha: Fix generic brk system call emulation in 
>> __brk_call (bug 29490)/
>> /37fd2ac665 stdlib: Fixup mbstowcs NULL __dst handling. [BZ #29279]/
>> /a1ec4157bc stdlib: Remove attr_write from mbstows if dst is NULL 
>> [BZ: 29265]/
>> /813a8d0171 Update syscall lists for Linux 5.19/
>> /e200127c6c riscv: Update rv64 libm test ulps/
>> /8c172a6cb0 dlfcn: Pass caller pointer to static dlopen 
>> implementation (bug 29446)/

Ideally you'd get that in this week since I think that 4.0.4 is being 
built on Monday, September 19th.

CCing Steve in case he missed this thread.


>> The binutils-2.38 has no new commits. And, gcc-11.x also not have any 
>> new release after 11.3.

That's good to know. I was just wondering if there was going to be 
gcc-11.4 so this info is timely.


>> In /master/ branch gcc_12.2, glibc_2.36 & binutils_2.39 versions are 
>> used. Kirkstone will continue to use the old versions?


To answer this more directly than Khem. ;-)

The Kirkstone branch will NOT update to the versions shown above. Users 
want a stable version

for the supported timeline of a release; some even may be surprised that 
we update from 11.2 to 11.3
even if it's all bug fixes.


>>
>
> the glibc fixes are good so go ahead bump the SRCREV to latest on 2.35 
> branch

Agreed.


>  major version backports are exceptions. We can consider doing mixin 
> layers if needed for say newer compiler.


Answered above.

Thanks Sundeep!

../Randy


>
>>
>>
>> Thanks,
>> Sundeep K.
>>
>>
>>
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#170603): https://lists.openembedded.org/g/openembedded-core/message/170603
> Mute This Topic: https://lists.openembedded.org/mt/92739561/3616765
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [randy.macleod@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

-- 
# Randy MacLeod
# Wind River Linux



  reply	other threads:[~2022-09-13 18:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  2:24 [kirkstone] binutils: stable 2.38 branch updates Sundeep KOKKONDA
2022-08-01  2:34 ` Sundeep KOKKONDA
2022-08-01 10:11 ` [OE-core] " Khem Raj
2022-09-13  9:43   ` Sundeep KOKKONDA
2022-09-13 16:59     ` [OE-core] " Khem Raj
2022-09-13 18:42       ` Randy MacLeod [this message]
2022-09-13 18:46         ` Khem Raj
2022-09-13 18:53         ` 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=7cd419c6-f3fc-6ebe-8dee-ee969d26e88a@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=steve@sakoman.com \
    --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