From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10136] New: can't compile systemd with GCC 7.X when optimization is on
Date: Wed, 26 Jul 2017 16:01:08 +0000 [thread overview]
Message-ID: <bug-10136-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10136
Bug ID: 10136
Summary: can't compile systemd with GCC 7.X when optimization
is on
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: yurovsky at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7131
--> https://bugs.busybox.net/attachment.cgi?id=7131&action=edit
workaround
Building systemd will fail due to a bug in GCC if we're using the buildroot GCC
7.X toolchain and have enable optimization (-O3). That is:
BR2_OPTIMIZE_3=y
BR2_GCC_VERSION_7_X=y
BR2_GCC_VERSION="7.1.0"
The problem is with GCC's nonnull detection (there's nothing wrong with the
systemd code in question) and it looks like it has been fixed upstream but we
don't have the backported fix in Buildroot:
https://github.com/systemd/systemd/issues/6119
A quick workaround is to patch systemd with the attached patch but it seems
that GCC should have some patches backported.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-07-26 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 16:01 bugzilla at busybox.net [this message]
2017-07-26 16:08 ` [Buildroot] [Bug 10136] can't compile systemd with GCC 7.X when optimization is on bugzilla at busybox.net
2017-07-26 16:25 ` bugzilla at busybox.net
2017-08-02 20:05 ` bugzilla at busybox.net
2017-08-02 20:35 ` bugzilla at busybox.net
2018-01-10 21:25 ` bugzilla at busybox.net
2018-01-11 17:17 ` bugzilla at busybox.net
2018-01-16 23:03 ` 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-10136-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