From: Anthony Green <green@moxielogic.com>
To: libffi-discuss@sourceware.org
Subject: libffi 3.2 and disruptive changes
Date: Tue, 11 Nov 2014 14:53:00 -0000 [thread overview]
Message-ID: <87wq71yej4.fsf@moxielogic.com> (raw)
I'd like to move ahead with Richard's proposed changes for GO, complex
types, and the numerous other clean ups he's proposed.
These changes will break msvc builds as well as iOS/OSX.
As long as we're breaking things, I'd like to use this opportunity to
change the header files so we have a shared set of .h files in
/usr/include.
Once things settle down from these changes, I'm hoping somebody can help
with the msvc and iOS/OSX ports.
In preparation for all of these changes, I've made a quick 3.2 release.
There were a few nice fixes that were sitting around in the tree, and
I'm not sure how long this next round of hacking will take.
The 3.2 release should be in pretty good shape *except* for the win32/64
msvc builds which are known to be broken. See
https://github.com/atgreen/libffi/issues/138 for details.
Thanks,
AG
next reply other threads:[~2014-11-11 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 14:53 Anthony Green [this message]
2014-11-11 14:59 ` James Greenhalgh
2014-11-12 12:04 ` Anthony Green
2014-11-11 15:01 ` Alan Lawrence
2014-11-12 7:16 ` Dominik Vogt
2014-11-12 7:22 ` Richard Henderson
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=87wq71yej4.fsf@moxielogic.com \
--to=green@moxielogic.com \
--cc=libffi-discuss@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).