From: Anthony Green <green@redhat.com>
To: libffi-discuss@sourceware.org
Subject: libffi 3.0.10rc4 available for testing
Date: Sat, 12 Feb 2011 14:44:00 -0000 [thread overview]
Message-ID: <m3vd0pz4yq.fsf@redhat.com> (raw)
I've posted rc4 is here:
ftp://sourceware.org/pub/libffi/libffi-3.0.10rc4.tar.gz
Changes this time round:
* configury changes to remove GCCisms for native AIX/Solaris/etc tool builds.
* running configure in the source directory automatically creates a
target specific build subdir
* debug code is only built when --enable-debug
* a testing tweaks, and other minor changes
The iOS build is known to be broken and native windows / mingw is
completely untested, but I think we're in pretty good shape otherwise.
We just need more test results:
http://www.moxielogic.org/wiki/index.php?title=Libffi_3.0.10
Thanks!
AG
next reply other threads:[~2011-02-12 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 14:44 Anthony Green [this message]
2011-02-12 16:12 ` Luis Lavena
2011-02-13 11:03 carlo.bramix
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=m3vd0pz4yq.fsf@redhat.com \
--to=green@redhat.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).