From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: libvirt-python: update to 5.9.0.
Date: Thu, 07 Nov 2019 10:44:42 +0100 [thread overview]
Message-ID: <20191107094442.fzafZvxrRDHMyhdKgVT9wfUp8xG9XniOAdCPSKq4UiM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16198@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/pull/16198#issuecomment-551003080
Comment:
Yeah, I suspect all python modules that contain C code and use distutils will. The issue is in sysconfig which uses the host python Makefile to get the build configuration and only appends additionally supplied flags to that to build the flags for the build. I suspect that was always the case and somehow ignored in earlier gcc versions at least I couldn't find a breaking change in the python source code.
I'm looking for a way to override this for cross builds without patching the Python source code but haven't found one yet.
next prev parent reply other threads:[~2019-11-07 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 8:11 [PR PATCH] " voidlinux-github
2019-11-07 9:33 ` voidlinux-github
2019-11-07 9:44 ` voidlinux-github [this message]
2019-11-07 9:46 ` voidlinux-github
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=20191107094442.fzafZvxrRDHMyhdKgVT9wfUp8xG9XniOAdCPSKq4UiM@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).