From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/5] package/binutils: disable gprofng support for each known unsupported version
Date: Sat, 1 Jul 2023 23:08:03 +0200 [thread overview]
Message-ID: <20230701230803.474f8570@windsurf> (raw)
In-Reply-To: <20230611131631.806432-1-romain.naour@gmail.com>
On Sun, 11 Jun 2023 15:16:27 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> While adding new binutils version, the gprofng support will
> no longer only available with one specific version.
>
> Instead disable gprofng explicitely for each binutils
> version that are know too old to support it.
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
> package/binutils/Config.in.host | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Series applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-01 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 13:16 [Buildroot] [PATCH 1/5] package/binutils: disable gprofng support for each known unsupported version Romain Naour
2023-06-11 13:16 ` [Buildroot] [PATCH 2/5] package/{binutils, gdb}: switch to https urls for archives hashes Romain Naour
2023-07-16 17:47 ` Peter Korsgaard
2023-06-11 13:16 ` [Buildroot] [PATCH 3/5] package/binutils: add support for version 2.40 Romain Naour
2023-06-11 13:16 ` [Buildroot] [PATCH 4/5] package/binutils: switch to 2.39.x as the default version Romain Naour
2023-06-11 13:16 ` [Buildroot] [PATCH 5/5] package/binutils: drop 2.37.x series Romain Naour
2023-07-01 21:08 ` Thomas Petazzoni via buildroot [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=20230701230803.474f8570@windsurf \
--to=buildroot@buildroot.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.