From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13236] Can't compile linux 5.4.8 (with gcc 10 on host)
Date: Mon, 05 Oct 2020 13:14:22 +0000 [thread overview]
Message-ID: <bug-13236-163-Si1YSaLaR9@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13236-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13236
Peter Korsgaard <jacmet@uclibc.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
This is indeed a Linux kernel bug and not really something we can do about
(unless this is one of out defconfigs?) as you can specify a custom Linux
kernel version.
The issue has been fixed in the upstream 5.4.x kernel since commit
35b34d264cb3479 (5.4.29):
commit 35b34d264cb347909ec89d9fa895900035d5438c
Author: Dirk Mueller <dmueller@suse.com>
Date: Tue Jan 14 18:53:41 2020 +0100
scripts/dtc: Remove redundant YYLOC global declaration
commit e33a814e772cdc36436c8c188d8c42d019fda639 upstream.
gcc 10 will default to -fno-common, which causes this error at link
time:
(.text+0x0): multiple definition of `yylloc'; dtc-lexer.lex.o (symbol
from plugin):(.text+0x0): first defined here
This is because both dtc-lexer as well as dtc-parser define the same
global symbol yyloc. Before with -fcommon those were merged into one
defintion. The proper solution would be to to mark this as "extern",
however that leads to:
dtc-lexer.l:26:16: error: redundant redeclaration of 'yylloc'
[-Werror=redundant-decls]
26 | extern YYLTYPE yylloc;
| ^~~~~~
In file included from dtc-lexer.l:24:
dtc-parser.tab.h:127:16: note: previous declaration of 'yylloc' was here
127 | extern YYLTYPE yylloc;
| ^~~~~~
cc1: all warnings being treated as errors
which means the declaration is completely redundant and can just be
dropped.
Signed-off-by: Dirk Mueller <dmueller@suse.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
[robh: cherry-pick from upstream]
Cc: stable at vger.kernel.org
Signed-off-by: Rob Herring <robh@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-10-05 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 10:35 [Buildroot] [Bug 13236] New: Can't compile linux 5.4.8 (with gcc 10 on host) bugzilla at busybox.net
2020-10-05 13:14 ` bugzilla at busybox.net [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=bug-13236-163-Si1YSaLaR9@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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