From: Anthony Green <green@moxielogic.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: libffi 3.0.12 rc2 ready for testing
Date: Fri, 08 Feb 2013 18:29:00 -0000 [thread overview]
Message-ID: <CACxje58XTXtvebdYj_dhsSRnEEm5VPPWhpSxQjt8bX63p56hGw@mail.gmail.com> (raw)
In-Reply-To: <51151008.878ec20a.286f.fffff628SMTPIN_ADDED_BROKEN@mx.google.com>
On Fri, Feb 8, 2013 at 9:47 AM, James Greenhalgh
<james.greenhalgh@arm.com> wrote:
> It looks like the RC1 and RC2 tarballs haven't picked up
> src/aarch64/sysv.S so the build is broken for the AArch64 target:
>
Thanks James. I've committed a fix that should make the next tarball work.
AG
next prev parent reply other threads:[~2013-02-08 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 23:10 Anthony Green
2013-02-08 14:27 ` Matthias Klose
2013-02-08 14:47 ` James Greenhalgh
2013-02-08 18:23 ` Peter Bergner
[not found] ` <51151008.878ec20a.286f.fffff628SMTPIN_ADDED_BROKEN@mx.google.com>
2013-02-08 18:29 ` Anthony Green [this message]
2013-02-08 20:41 ` Matthias Klose
2013-02-08 20:46 ` Andreas Tobler
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=CACxje58XTXtvebdYj_dhsSRnEEm5VPPWhpSxQjt8bX63p56hGw@mail.gmail.com \
--to=green@moxielogic.com \
--cc=james.greenhalgh@arm.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).