From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kconfig warnings with GCC9
Date: Thu, 6 Feb 2020 21:22:32 +0100 [thread overview]
Message-ID: <20200206212232.5262c903@windsurf> (raw)
In-Reply-To: <CAGt4E5vMQgJKAKfFgr7oUmMJjyDufB72L7VVUgS-UGg8g6c+_A@mail.gmail.com>
Hello Markus,
On Thu, 6 Feb 2020 10:30:28 -0800
Markus Mayer <markus.mayer@broadcom.com> wrote:
> > That's kernel 5.4. Kconfig itself complains about a few Kconfig values
> > for my stock kernel (maybe because that's 5.3?), but the compiler is
> > fine. So we should be good.
>
> Okay. I poked around some more. Turns out that kconfig on the Linux
> side changed *a lot* between 4.17-rc2 and 5.5. Many files were
> renamed. A good number of functions was rewritten (partially precisely
> to avoid the format-overflow warnings). The easiest approach might
> just be to take the Linux kconfig implementation as is and re-apply
> the Buildroot customizations on top of the new implementation rather
> than trying to merge in all the changes from Linux and risking
> breakage by doing that incorrectly.
This easiest approach is what we do every time we update the Kconfig
code in Buildroot.
> Is there an easy-ish way to see all the customizations that Buildroot
> did to kconfig over the years (excluding code changes imported from
> Linux during past kconfig upgrades)?
See support/kconfig/patches/ and support/kconfig/README.buildroot.
Looking forward to the bump of our Kconfig code base!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-02-06 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 19:17 [Buildroot] Kconfig warnings with GCC9 Markus Mayer
2020-01-10 20:56 ` Thomas Petazzoni
2020-01-10 22:35 ` Markus Mayer
2020-01-11 8:32 ` Peter Korsgaard
2020-01-11 17:59 ` Markus Mayer
[not found] ` <CAGt4E5vMQgJKAKfFgr7oUmMJjyDufB72L7VVUgS-UGg8g6c+_A@mail.gmail.com>
2020-02-06 20:22 ` Thomas Petazzoni [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=20200206212232.5262c903@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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