From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next 0/4] Upgrade to Binutils 2.42
Date: Sun, 3 Mar 2024 11:50:41 +0100 [thread overview]
Message-ID: <ZeRWAXh2NYMm-uSl@landeda> (raw)
In-Reply-To: <20240303084014.156991-1-thomas.petazzoni@bootlin.com>
Thomas, All,
On 2024-03-03 09:40 +0100, Thomas Petazzoni via buildroot spake thusly:
> This series of patches update binutils to version 2.42, doing the
> usual dance:
>
> 1. Add 2.42
> 2. Make 2.41 the default
> 3. Drop 2.39
>
> An fourth patch is added to drop some code that is no longer needed
> now that binutils 2.39 is gone.
I've made some comments on two patches, to which I individually replied
already. Whole series applied to next, thanks.
Regards,
Yann E. MORIN.
> Thomas
>
> Thomas Petazzoni (4):
> package/binutils: add support for 2.42
> package/binutils: make 2.41 the default version
> package/binutils: drop support for binutils 2.39
> package/binutils: drop BR2_PACKAGE_BINUTILS_HAS_NO_LIBSFRAME
>
> .checkpackageignore | 3 -
> Config.in.legacy | 6 +
> ...or1k-fix-building-with-gcc-version-5.patch | 50 ------
> .../{2.39 => 2.42}/0001-sh-conf.patch | 14 +-
> .../0002-poison-system-directories.patch | 167 ++++++++++--------
> package/binutils/Config.in.host | 14 +-
> package/binutils/binutils.hash | 1 -
> package/binutils/binutils.mk | 10 +-
> package/elf2flt/elf2flt.mk | 2 +-
> 9 files changed, 111 insertions(+), 156 deletions(-)
> delete mode 100644 package/binutils/2.39/0003-bfd-elf32-or1k-fix-building-with-gcc-version-5.patch
> rename package/binutils/{2.39 => 2.42}/0001-sh-conf.patch (82%)
> rename package/binutils/{2.39 => 2.42}/0002-poison-system-directories.patch (79%)
>
> --
> 2.43.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-03-03 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 8:40 [Buildroot] [PATCH next 0/4] Upgrade to Binutils 2.42 Thomas Petazzoni via buildroot
2024-03-03 8:40 ` [Buildroot] [PATCH next 1/4] package/binutils: add support for 2.42 Thomas Petazzoni via buildroot
2024-03-03 9:31 ` Yann E. MORIN
2024-03-03 8:40 ` [Buildroot] [PATCH next 2/4] package/binutils: make 2.41 the default version Thomas Petazzoni via buildroot
2024-03-03 8:40 ` [Buildroot] [PATCH next 3/4] package/binutils: drop support for binutils 2.39 Thomas Petazzoni via buildroot
2024-03-03 10:49 ` Yann E. MORIN
2024-03-03 8:40 ` [Buildroot] [PATCH next 4/4] package/binutils: drop BR2_PACKAGE_BINUTILS_HAS_NO_LIBSFRAME Thomas Petazzoni via buildroot
2024-03-03 10:50 ` Yann E. MORIN [this message]
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=ZeRWAXh2NYMm-uSl@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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