From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: python-numpy: fix for armv5tel-musl.
Date: Wed, 06 Jan 2021 18:26:58 +0100 [thread overview]
Message-ID: <20210106172658.6Yic3X-ADnfwPjzEW-ad7w4DEkSQn20n4DxKTyWcQOs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24988@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
There's a closed pull request on the void-packages repository
python-numpy: fix for armv5tel-musl.
https://github.com/void-linux/void-packages/pull/24988
Description:
in fenv.h, musl disables the normal set of constants that you would get
on arm with an arm device with an fpu (armv6 and up), but armv5tel on
void uses softfloat all the time. But python3-numpy dosen't use these to
interact with the fpu (the compiler would generate those instructions)
and rather just uses those constants for a generic GCC implementation.
So we give them out anyway.
python-numpy uses the same patch from python3-numpy.
prev parent reply other threads:[~2021-01-06 17:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 8:18 [PR PATCH] " fosslinux
2020-09-20 8:40 ` [PR PATCH] [Updated] " fosslinux
2020-09-20 8:40 ` fosslinux
2020-09-22 6:04 ` [PR PATCH] [Updated] " fosslinux
2020-09-25 0:31 ` [PR REVIEW] " sgn
2020-09-25 8:10 ` fosslinux
2020-09-29 4:39 ` [PR PATCH] [Updated] " fosslinux
2020-10-01 22:52 ` fosslinux
2020-10-09 20:21 ` [PR REVIEW] " ericonr
2020-10-10 2:41 ` fosslinux
2020-10-10 2:59 ` [PR PATCH] [Updated] " fosslinux
2020-10-10 4:21 ` [PR REVIEW] " ericonr
2020-10-10 10:20 ` fosslinux
2020-12-01 0:27 ` sgn
2020-12-01 0:43 ` sgn
2020-12-01 0:47 ` sgn
2020-12-01 1:10 ` ericonr
2020-12-09 5:08 ` [PR REVIEW] " ahesford
2020-12-09 7:17 ` fosslinux
2020-12-31 1:06 ` [PR PATCH] [Updated] " fosslinux
2020-12-31 1:22 ` fosslinux
2020-12-31 1:22 ` [PR REVIEW] " fosslinux
2020-12-31 1:22 ` fosslinux
2020-12-31 17:59 ` ahesford
2020-12-31 23:34 ` fosslinux
2020-12-31 23:37 ` [PR PATCH] [Updated] " fosslinux
2021-01-06 16:26 ` ahesford
2021-01-06 17:26 ` ahesford [this message]
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=20210106172658.6Yic3X-ADnfwPjzEW-ad7w4DEkSQn20n4DxKTyWcQOs@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).