From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/2] package/{binutils, libiberty}: add support for version 2.41
Date: Tue, 1 Aug 2023 00:13:06 +0200 [thread overview]
Message-ID: <20230801001306.19ae77b4@windsurf> (raw)
In-Reply-To: <20230731183731.2978383-2-bernd@kuhls.net>
Hello Bernd,
On Mon, 31 Jul 2023 20:37:31 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Release notes:
> https://sourceware.org/pipermail/binutils/2023-July/128719.html
>
> Copied patches from version 2.40.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
This needs a bit more work, look at other binutils bumps. We want at
least:
- Introduce 2.41
- Switch to 2.40 as default
- Drop 2.38 (don't forget legacy handling)
Also, do we want to update libiberty to 2.41 as well? (Need to make
sure it remains compatible with binutils 2.39 and 2.40).
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-31 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 18:37 [Buildroot] [PATCH v2 1/2] package/binutils: install libsframe to staging Bernd Kuhls
2023-07-31 18:37 ` [Buildroot] [PATCH v2 2/2] package/{binutils, libiberty}: add support for version 2.41 Bernd Kuhls
2023-07-31 22:13 ` Thomas Petazzoni via buildroot [this message]
2023-07-31 22:11 ` [Buildroot] [PATCH v2 1/2] package/binutils: install libsframe to staging Thomas Petazzoni via buildroot
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=20230801001306.19ae77b4@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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