From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10551] New: PowerPC SPE and Musl
Date: Tue, 05 Dec 2017 18:20:12 +0000 [thread overview]
Message-ID: <bug-10551-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10551
Bug ID: 10551
Summary: PowerPC SPE and Musl
Product: buildroot
Version: 2017.08
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: sigurd.segtnan at kongsberg.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7411
--> https://bugs.busybox.net/attachment.cgi?id=7411&action=edit
diff for package/gcc/gcc.mk (and Config.in in toolchain)
Musl is not supported for PowerPC SPE according to
toolchain/toolchain-buildroot/Config.in line 74: "depens on !BR2_powerpc_SPE #
not supported, build breaks". This breakage may be due the
"--with-long-double-128" in package/gcc/gcc.mk, since we have not experienced
any build breakage when we changed lines 241-245 to
ifeq ($(BR2_powerpc_SPE),y)
ifeq ($(BR2_TOOLCHAIN_USES_MUSL),n)
HOST_GCC_COMMON_CONF_OPTS += \
--enable-e500_double \
--with-long-double-128
endif
else
HOST_GCC_COMMON_CONF_OPTS += \
--enable-e500_double \
--with-long-double-64 \
--enable-secureplt
endif
We have used this without problems since buildroot 2016.05 (tested with gcc 6.x
and gcc 7.x).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-12-05 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 18:20 bugzilla at busybox.net [this message]
2018-01-10 20:20 ` [Buildroot] [Bug 10551] PowerPC SPE and Musl bugzilla at busybox.net
2018-01-11 19:17 ` bugzilla at busybox.net
2018-01-16 22:28 ` bugzilla at busybox.net
2018-01-17 9:52 ` bugzilla at busybox.net
2020-05-17 18:54 ` bugzilla at busybox.net
2020-05-17 21:01 ` bugzilla at busybox.net
2022-12-04 16:21 ` bugzilla
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-10551-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