From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Edgar Bonet <bonet@grenoble.cnrs.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Binutils 2.41 cannot compile old Linux kernels
Date: Sat, 6 Apr 2024 23:34:44 +0200 [thread overview]
Message-ID: <20240406233444.3e78ce4b@windsurf> (raw)
In-Reply-To: <4570d0d7-b1b8-412d-a3f8-957ee8b0dfc9@grenoble.cnrs.fr>
Hello Edgar,
Thanks for having looked into this issue. See below some feedback.
On Sat, 6 Apr 2024 21:32:46 +0200
Edgar Bonet <bonet@grenoble.cnrs.fr> wrote:
> Another option would be to bump the kernel version, but I assume this
> should be done (and tested) by the maintainers of the affected
> defconfigs.
This is definitely the right thing. If those maintainers are no longer
available, it means those defconfigs are unmaintained and should be
dropped.
In my opinion, this is actually a good side effect of those toolchain
changes: they allow from time to time to detect that some defconfigs
are bitrotting, without being maintained, and encourages us to revisit
the relevance of such defconfigs in Buildroot.
Best regards,
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
prev parent reply other threads:[~2024-04-06 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 19:32 [Buildroot] Binutils 2.41 cannot compile old Linux kernels Edgar Bonet
2024-04-06 21:34 ` 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=20240406233444.3e78ce4b@windsurf \
--to=buildroot@buildroot.org \
--cc=bonet@grenoble.cnrs.fr \
--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