Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13331] New: openrc-0.42.1 compilation failure on gcc-10
Date: Mon, 23 Nov 2020 16:27:20 +0000	[thread overview]
Message-ID: <bug-13331-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 13331
           Summary: openrc-0.42.1 compilation failure on gcc-10
           Product: buildroot
           Version: 2020.08.2
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: mscdex at mscdex.net
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 8676
  --> https://bugs.busybox.net/attachment.cgi?id=8676&action=edit
Fix for GCC 10

Host machine: Ubuntu 18.04
Buildroot version: 2020.08.2
Target: i586-buildroot-linux-musl-gcc (GCC 10.2.0)

Trying to build OpenRC 0.42.1 fails when compiling with GCC 10.x. It evidently
will also fail with prior major versions when the '-fno-common' flag is
explicitly used (this flag seems to be the default now on GCC 10.x, hence the
failure).

I've attached a patch I found from Gentoo that fixes this issue.

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

             reply	other threads:[~2020-11-23 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 16:27 bugzilla at busybox.net [this message]
2020-11-23 16:37 ` [Buildroot] [Bug 13331] openrc-0.42.1 compilation failure on gcc-10 bugzilla at busybox.net
2020-11-23 19:20 ` bugzilla at busybox.net
2020-11-23 21:48 ` 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-13331-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox