From: "Paul Monson via libffi-discuss" <libffi-discuss@sourceware.org>
To: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Windows ARM32 support
Date: Tue, 16 Apr 2019 01:46:00 -0000 [thread overview]
Message-ID: <CY4PR2101MB0804CF78D1B16D37CA31EC05F9240@CY4PR2101MB0804.namprd21.prod.outlook.com> (raw)
Hi,
Is it possible to merge https://github.com/libffi/libffi/issues/479 soon?
This would enable using an unpatched libffi with CPython on windows.
The appveyor build includes successfully building for Windows arm32 with this change.
The travis failure doesn't appear to be related to this change to me, but if it is I would like to
Thanks,
Paul
reply other threads:[~2019-04-16 1:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CY4PR2101MB0804CF78D1B16D37CA31EC05F9240@CY4PR2101MB0804.namprd21.prod.outlook.com \
--to=libffi-discuss@sourceware.org \
--cc=Paul.Monson@microsoft.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).