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:46:09 +0100 [thread overview]
Message-ID: <20191107094609.mG0CK8vhPNZcImRXZ3dzI-kxPI9QufvWKk5wjvqqs2c@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: 1315 bytes --]
New comment by ndowens on void-packages repository
https://github.com/void-linux/void-packages/pull/16198#issuecomment-551003602
Comment:
Yeah I have been trying things on ones I have came across but no luck so far
On Thu, Nov 7, 2019 at 3:44 AM Helmut Pozimski <notifications@github.com>
wrote:
> 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.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/pull/16198?email_source=notifications&email_token=AAA4X3ZIVVUBGAKK4XLOGQDQSPPQZA5CNFSM4JKC6ZNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDL2HSA#issuecomment-551003080>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAA4X3Y575NZEZSAHEPHWITQSPPQZANCNFSM4JKC6ZNA>
> .
>
prev parent reply other threads:[~2019-11-07 9:46 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
2019-11-07 9:46 ` voidlinux-github [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=20191107094609.mG0CK8vhPNZcImRXZ3dzI-kxPI9QufvWKk5wjvqqs2c@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).