public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: "Hannes Müller" <h.c.f.mueller@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: libffi: upgrade to libffi-3.4.3 proposed (cygport file attached)
Date: Sat, 08 Oct 2022 20:26:42 +0200	[thread overview]
Message-ID: <f7d7240eacb93f4e33d25547bb29688d2d257934.camel@gmail.com> (raw)
In-Reply-To: <93f7b9bc-43d1-00de-fca2-5ae762909022@dronecode.org.uk>

Hi John,

I'm not sure. So far I would not recommend to upgrade to libffi-3.4.3
for Cygwin i686.

Currently MSYS2 makes only builts for x86_64. The 32 bit version builts
are only MinGW variants.

Test for Cygwin on i686 is not in CI of libffi maintainer Anthony
Green, e.g.https://github.com/libffi/libffi/pull/728

Maybe you open an Issue on https://github.com/libffi/libffi/issues
Anthony Green is very responsive.

Thanks,
Hannes



Am Samstag, dem 08.10.2022 um 13:47 +0100 schrieb Jon Turney:
> On 04/10/2022 19:11, Hannes Müller wrote:
> > Dear Maintainer(s),
> > 
> > libffi is ORPHANED and outdated.
> > 
> > Attached a cygport for newest libffi-3.4.3, which needs no extra
> > patches.
> > 
> > PS: libffi-3.4.3 is also used on MSYS2 without extra patches.
> > 
> > Thanks!
> 
> Thanks.
> 
> I'm minded to do a NMU of libffi using your revised cygport, but I 
> notice that many tests fail on x86 (see [1]).  Is this expected, or
> does 
> it indicate some problem there?
> 
> [1] 
> https://github.com/cygwin/scallywag/actions/runs/3205410540/jobs/5237942271#step:6:2343
> 



      reply	other threads:[~2022-10-08 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <23b4f0439c8123bffa09fda381929c216aaeeee0.camel@gmail.com>
2022-10-08 12:47 ` Jon Turney
2022-10-08 18:26   ` Hannes Müller [this message]

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=f7d7240eacb93f4e33d25547bb29688d2d257934.camel@gmail.com \
    --to=h.c.f.mueller@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /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).