From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kconfig warnings with GCC9
Date: Sat, 11 Jan 2020 09:32:40 +0100 [thread overview]
Message-ID: <87a76ujsuv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAGt4E5u+KA3Vi0dp+YRAYnvXSJN1XXF=S86Th4NoyamnQSWpiw@mail.gmail.com> (Markus Mayer's message of "Fri, 10 Jan 2020 14:35:37 -0800")
>>>>> "Markus" == Markus Mayer <mmayer@broadcom.com> writes:
> On Fri, 10 Jan 2020 at 12:56, Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
>>
>> Hello,
>>
>> On Fri, 10 Jan 2020 11:17:47 -0800
>> Markus Mayer <mmayer@broadcom.com> wrote:
>>
>> > Hi all,
>> >
>> > Using GCC9 (Ubuntu 19.10), I am getting some compiler warnings
>> > (potential buffer overruns) in the Kconfig code. Is this a known
>> > issue?
>>
>> You can try to update the kconfig code in Buildroot with the kconfig
>> code available from the latest kernel, and see if it fixes the
>> warnings. We're currently using the kconfig code from 4.17-rc2 it seems.
> I'll give it a shot.
Before doing that, try running make menuconfig with a recent Linux
kernel to check if those warnings are no longer triggered.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-01-11 8:32 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 [this message]
2020-01-11 17:59 ` Markus Mayer
[not found] ` <CAGt4E5vMQgJKAKfFgr7oUmMJjyDufB72L7VVUgS-UGg8g6c+_A@mail.gmail.com>
2020-02-06 20:22 ` Thomas Petazzoni
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=87a76ujsuv.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.