From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: numpy headers symlink breaks using numpy in a venv
Date: Wed, 09 Mar 2022 19:39:17 +0100 [thread overview]
Message-ID: <20220309183917.0EJBo8Bb7PY_yMyflKcxXSMRp6dEfroudvAW-gE1-Dw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36062@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/36062#issuecomment-1063239193
Comment:
I agree that these links are problematic.
This is probably a hack around path issues for cross-builds that compile C extensions with Numpy headers that is no longer necessary. I took some care to properly order CFLAGS in the numpy build helper; hopefully we can just drop the links.
I think there is a new Numpy release; we can bump the version, drop the symlinks and test some packages that rely on the build helper to confirm that everything works as expected.
next prev parent reply other threads:[~2022-03-09 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 15:05 [ISSUE] " tornaria
2022-03-09 15:06 ` tornaria
2022-03-09 16:27 ` tornaria
2022-03-09 17:28 ` tornaria
2022-03-09 18:39 ` ahesford [this message]
2022-03-09 20:33 ` [ISSUE] [CLOSED] " ahesford
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=20220309183917.0EJBo8Bb7PY_yMyflKcxXSMRp6dEfroudvAW-gE1-Dw@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).