From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [WIP] python3-scikit-image: update to 0.21.0
Date: Tue, 06 Jun 2023 17:02:10 +0200 [thread overview]
Message-ID: <20230606150210.dxhE1i7WoN73svNv_oXO8FNfE_At_Dd99tzy-yTjbpk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44233@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
There's a closed pull request on the void-packages repository
[WIP] python3-scikit-image: update to 0.21.0
https://github.com/void-linux/void-packages/pull/44233
Description:
@eli-schwartz I wonder if you can offer some insight. To get Meson building scikit-image, I patched the `meson.build` to allow manual specification of include directories for NumPy and Pythran rather than forcing the build system to execute the Python interpreter. This works OK and was stolen from SciPy. However:
- Cross-building on 32-bit hosts from 64-but builders fails because `LONG_BIT` is the wrong size in Python's `python3.11/pyport.h`. Clearly some headers are mixing. This gets pulled in by Pythran's generated outputs in a couple of places.
- I can't seem to get `-I/usr/include/python3.11` out of the compiler flags, when it should point to the cross-build tree.
- I don't know that fixing the include path is sufficient to resolve the first problem.
Although I'm prepared to leave 32-but ARM behind with this update, I'd prefer to get it working correctly.
next prev parent reply other threads:[~2023-06-06 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 22:42 [PR PATCH] " ahesford
2023-06-02 23:53 ` eli-schwartz
2023-06-03 2:58 ` ahesford
2023-06-03 2:59 ` ahesford
2023-06-06 14:06 ` [PR PATCH] [Updated] " ahesford
2023-06-06 14:23 ` ahesford
2023-06-06 14:43 ` ahesford
2023-06-06 14:45 ` [PR PATCH] [Updated] " ahesford
2023-06-06 15:02 ` ahesford [this message]
2023-06-06 15:02 ` ahesford
2023-06-06 15:05 ` eli-schwartz
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=20230606150210.dxhE1i7WoN73svNv_oXO8FNfE_At_Dd99tzy-yTjbpk@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).