From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Romain Naour <romain.naour@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next 1/4] package/binutils: add support for 2.42
Date: Sun, 3 Mar 2024 10:31:14 +0100 [thread overview]
Message-ID: <ZeRDYucecDd7bgzn@landeda> (raw)
In-Reply-To: <20240303084014.156991-2-thomas.petazzoni@bootlin.com>
Thomas, All,
On 2024-03-03 09:40 +0100, Thomas Petazzoni via buildroot spake thusly:
[--SNIP--]
> diff --git a/package/binutils/Config.in.host b/package/binutils/Config.in.host
> index 2f1ddf4bdc..f1cc175cf9 100644
> --- a/package/binutils/Config.in.host
> +++ b/package/binutils/Config.in.host
> @@ -25,6 +25,9 @@ config BR2_BINUTILS_VERSION_2_40_X
> config BR2_BINUTILS_VERSION_2_41_X
> bool "binutils 2.41"
>
> +config BR2_BINUTILS_VERSION_2_42_X
> + bool "binutils 2.42"
> +
> config BR2_BINUTILS_VERSION_ARC
> bool "binutils arc (2.41)"
> depends on BR2_arc
I know that the arc variant is just a whart in the list, but it feels
odd, when arc is enabled, to have list not sorted by actual versions:
2.40
2.41
2.42
arc (2.41)
I think we'd like to have the list neatly ordered by version...
This is a very minor comment, of course...
Regards,
Yann E. MORIN.
> @@ -37,6 +40,7 @@ config BR2_BINUTILS_VERSION
> default "2.39" if BR2_BINUTILS_VERSION_2_39_X
> default "2.40" if BR2_BINUTILS_VERSION_2_40_X
> default "2.41" if BR2_BINUTILS_VERSION_2_41_X
> + default "2.42" if BR2_BINUTILS_VERSION_2_42_X
>
> config BR2_BINUTILS_GPROFNG
> bool "gprofng support"
> --
> 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
next prev parent reply other threads:[~2024-03-03 9:31 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 [this message]
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 ` [Buildroot] [PATCH next 0/4] Upgrade to Binutils 2.42 Yann E. MORIN
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=ZeRDYucecDd7bgzn@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--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