From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Robert Marko <robimarko@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] kconfig/lxdialog: fix check() with GCC14
Date: Tue, 9 Apr 2024 21:46:56 +0200 [thread overview]
Message-ID: <20240409214656.721dc7c3@windsurf> (raw)
In-Reply-To: <20240408213807.GA44146@pevik>
On Mon, 8 Apr 2024 23:38:07 +0200
Petr Vorel <petr.vorel@gmail.com> wrote:
> FYI I gave up kconfig update after big rewrites in the Linux kernel
> made by Masahiro Yamada (the new kbuild and kconfig maintainer), because the
> code changes were quite big but kconfig in Buildroot is IMHO not missing any
> significant usability function. But I can be wrong, Thomas let me know if you
> miss something significant which would justify the update. Obviously we would
> get some fixes, but also major rewrite, which would likely require changes in
> other parts of Buildroot.
I have no idea what are the new interesting features that have been
added in the upstream scripts/kconfig/ (if any). However, keeping our
support/kconfig/ reasonably up-to-date is not only about new features,
it's also about staying compatible with reasonably recent
libraries/tools (more recent ncurses, Gtk, Qt, more recent GCC, like
this issue illustrates).
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
next prev parent reply other threads:[~2024-04-09 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:18 [Buildroot] [PATCH 1/1] kconfig/lxdialog: fix check() with GCC14 Robert Marko
2024-04-03 16:28 ` Petr Vorel
2024-04-08 20:36 ` Thomas Petazzoni via buildroot
2024-04-08 21:15 ` Robert Marko
2024-04-08 21:38 ` Petr Vorel
2024-04-09 19:46 ` Thomas Petazzoni via buildroot [this message]
2024-04-09 20:50 ` Yann E. MORIN
2024-04-11 0:15 ` Petr Vorel
2024-04-11 5:02 ` 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=20240409214656.721dc7c3@windsurf \
--to=buildroot@buildroot.org \
--cc=petr.vorel@gmail.com \
--cc=robimarko@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.