From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10551] PowerPC SPE and Musl
Date: Thu, 11 Jan 2018 19:17:00 +0000 [thread overview]
Message-ID: <bug-10551-163-Q99fqRAeKJ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10551-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10551
--- Comment #2 from sigurd.segtnan at kongsberg.com ---
I have asked around, and we used the information from from
https://wiki.musl-libc.org/supported-platforms.html. Since we found something
that worked for the PowerPC we used, we did not investigate further.
Today the relevant part under Supported target architectures (ABIs) is:
* powerpc (needs gcc built with ?enable-secureplt ?with-long-double-64, and
-Wl,?secure-plt to link dynamic binaries.)
* powerpc64
The "-Wl,?secure-plt" is probably for older versions of gcc (secure-plt is
mentioned in the 900-musl-support.patch fotr gcc 4.9.4, and "Pass --secure-plt
to the linker" seems to have been added to gcc in 2015 according to
https://gcc.gnu.org/ml/gcc-patches/2015-10/msg01501.html).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-01-11 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 18:20 [Buildroot] [Bug 10551] New: PowerPC SPE and Musl bugzilla at busybox.net
2018-01-10 20:20 ` [Buildroot] [Bug 10551] " bugzilla at busybox.net
2018-01-11 19:17 ` bugzilla at busybox.net [this message]
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-Q99fqRAeKJ@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