Skip to contentSkip to conversation

New: openrc-0.42.1 compilation failure on gcc-10

Buildroot bugzilla at busybox.net 1 participant 4 messages Nov 23, 2020

lore
Share & tools
lore
#0 lore 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.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#2 lore raw

[Buildroot] [Bug 13331] openrc-0.42.1 compilation failure on gcc-10

In reply to bugzilla at busybox.net

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

--- Comment #1 from Heiko Thiery <[email protected]> --- I send a patch for including the fix.

https://patchwork.ozlabs.org/project/buildroot/patch/20201123191729.2557-1-heiko.thiery at gmail.com/

Thank you

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#3 lore raw

[Buildroot] [Bug 13331] openrc-0.42.1 compilation failure on gcc-10

In reply to bugzilla at busybox.net

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

Peter Korsgaard <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Peter Korsgaard <[email protected]> --- Fixed in master by Heiko's patch, thanks

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.