From: Anthony Green <green@moxielogic.com>
To: Samuli Suominen <ssuominen@gentoo.org>
Cc: libffi-discuss@sourceware.org
Subject: Re: libffi 3.1-rc1 needs testing!
Date: Fri, 28 Mar 2014 15:43:00 -0000 [thread overview]
Message-ID: <87a9ca8h2p.fsf@moxielogic.com> (raw)
In-Reply-To: <53341E7D.1020408@gentoo.org> (Samuli Suominen's message of "Thu, 27 Mar 2014 14:50:05 +0200")
Samuli Suominen <ssuominen@gentoo.org> writes:
> On 25/03/14 23:10, Anthony Green wrote:
>> It's here: ftp://sourceware.org/pub/libffi/libffi-3.1-rc1.tar.gz
>>
>>
>
> Another missing patch from the release:
Thanks Samuli. I am applying both patches.
AG
>
> https://sourceware.org/ml/libffi-discuss/2014/msg00028.html
>
> It's an important one, at least for distributions building for multiple
> different arch's (like 32bit vs. 64bit)
> at the same time, important for eg. Gentoo's libffi
> Otherwise flags like eg. -m32 will be skipped and
> -print-multi-os-directory gives wrong value
next prev parent reply other threads:[~2014-03-28 15:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 23:49 libffi 3.0.14-rc0 " Anthony Green
2014-03-01 23:56 ` Anthony Green
2014-03-03 12:44 ` Dominik Vogt
2014-03-03 19:17 ` David Fang
2014-03-04 7:29 ` Will Newton
2014-03-05 0:31 ` Alan Hourihane
2014-03-04 22:14 ` Matthias Klose
2014-03-25 21:11 ` libffi 3.1-rc1 " Anthony Green
2014-03-27 12:23 ` Dominik Vogt
2014-03-27 12:25 ` Dominik Vogt
2014-03-27 12:31 ` Dominik Vogt
2014-03-27 12:40 ` Samuli Suominen
2014-03-27 12:45 ` Samuli Suominen
2014-03-27 12:55 ` Samuli Suominen
2014-03-28 15:43 ` Anthony Green [this message]
2014-03-28 15:05 ` James Greenhalgh
2014-03-28 17:33 ` Anthony Green
2014-04-24 12:47 ` Marcus Shawcroft
2014-03-28 20:37 ` Andreas Tobler
2014-03-28 20:39 ` Matthias Klose
2014-03-28 21:56 ` Anthony Green
2014-03-28 22:31 ` Anthony Green
2014-03-29 14:25 ` ABI breakage (Was: libffi 3.1-rc1 needs testing!) Anthony Green
2014-05-30 12:21 ` Matthias Klose
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=87a9ca8h2p.fsf@moxielogic.com \
--to=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
--cc=ssuominen@gentoo.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).