From: Anthony Green <green@moxielogic.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: libffi-discuss <libffi-discuss@sourceware.org>
Subject: Re: libffi 3.3 release candidate 1
Date: Tue, 26 Nov 2019 23:25:00 -0000 [thread overview]
Message-ID: <CACxje58k47Q2ukvXQ=p1coRidY8vAysWx+4k_A7A-jUeR9unLQ@mail.gmail.com> (raw)
In-Reply-To: <558abfbb-d3a5-d0ed-f2d1-c7aee5bb9de7@ubuntu.com>
Here you go. https://paste.centos.org/view/83f87106
On Tue, Nov 26, 2019 at 3:39 AM Matthias Klose <doko@ubuntu.com> wrote:
>
> On 08.11.19 15:27, Anthony Green wrote:
> > Thanks, Matthias, this is incredibly helpful.
> >
> > For ecl, it looks like they are using FFI_UNIX64 on the 32-bit x86, and
> > similar for amd64. This is easy to fix, and I'll submit a patch to
> > upstream ecl.
>
> please could you point me to this patch, or attach it here?
>
> Matthias
>
>
next prev parent reply other threads:[~2019-11-26 23:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:17 Anthony Green
2019-10-25 10:08 ` Matthias Klose
2019-10-25 10:29 ` John Paul Adrian Glaubitz
2019-10-25 14:41 ` Andreas Schwab
2019-10-25 14:44 ` John Paul Adrian Glaubitz
2019-10-25 18:32 ` Andreas Schwab
2019-10-25 18:37 ` John Paul Adrian Glaubitz
2019-10-25 19:04 ` Andreas Schwab
2019-10-25 19:07 ` John Paul Adrian Glaubitz
2019-10-26 11:35 ` Anthony Green
2019-10-26 12:54 ` Anthony Green
2019-10-31 19:49 ` Anthony Green
2019-10-31 20:32 ` John Paul Adrian Glaubitz
[not found] ` <CAAs=koj3HU08uxx36809NcPYe33xvEjUDsLwJc_9R8V4tbr9Zg@mail.gmail.com>
2019-10-31 22:16 ` John Paul Adrian Glaubitz
2019-11-01 8:01 ` John Paul Adrian Glaubitz
2019-11-01 22:24 ` John Paul Adrian Glaubitz
2019-11-08 9:21 ` Matthias Klose
2019-11-08 14:28 ` Anthony Green
2019-11-09 16:04 ` Matthias Klose
2019-11-09 17:46 ` Anthony Green
2019-11-10 16:22 ` Matthias Klose
2019-11-26 8:39 ` Matthias Klose
2019-11-26 23:25 ` Anthony Green [this message]
2019-11-27 7:54 ` Matthias Klose
2019-11-27 9:28 ` Anthony Green
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='CACxje58k47Q2ukvXQ=p1coRidY8vAysWx+4k_A7A-jUeR9unLQ@mail.gmail.com' \
--to=green@moxielogic.com \
--cc=doko@ubuntu.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).