All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13236] New: Can't compile linux 5.4.8 (with gcc 10 on host)
Date: Mon, 05 Oct 2020 10:35:00 +0000	[thread overview]
Message-ID: <bug-13236-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13236

            Bug ID: 13236
           Summary: Can't compile linux 5.4.8 (with gcc 10 on host)
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: cedric.chepied at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

I'm trying to build an image for olimex olinuxino maxi board.

Linux 5.4.8 build fails with this error:

/usr/bin/ld?: scripts/dtc/dtc-parser.tab.o:(.bss+0x20)?: multiple definitions
of ??yylloc??;

It looks very similar to this problem which seems to be solved for dtc package:

https://git.busybox.net/buildroot/commit/?id=198db470a73c14191915f8374362bc2a8b08c2bf

I solved it by applying this modification in linux build directory:
https://git.kernel.org/pub/scm/utils/dtc/dtc.git/commit/?id=0e9225eb0dfec51def612b928d2f1836b092bc7e

I don't know if this is a Linux bug or if it is fixed and you just have to pick
a new version.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-10-05 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 10:35 bugzilla at busybox.net [this message]
2020-10-05 13:14 ` [Buildroot] [Bug 13236] Can't compile linux 5.4.8 (with gcc 10 on host) bugzilla at busybox.net

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@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 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.