public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hannes Müller" <h.c.f.mueller@gmail.com>
To: cygwin@cygwin.com
Subject: libffi: upgrade to libffi-3.4.3 proposed (cygport file attached)
Date: Tue, 04 Oct 2022 20:11:53 +0200	[thread overview]
Message-ID: <23b4f0439c8123bffa09fda381929c216aaeeee0.camel@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 209 bytes --]

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!

Hannes

[-- Attachment #2: libffi.cygport --]
[-- Type: text/plain, Size: 719 bytes --]

NAME="libffi"
VERSION=3.4.3
RELEASE=1
CATEGORY="Libs"
SUMMARY="Portable foreign function interface library"
DESCRIPTION="The libffi library provides a portable, high level programming
interface to various calling conventions. This allows a programmer to call any
function specified by a call interface description at run-time."
HOMEPAGE="http://sourceware.org/libffi/"
SRC_URI="https://github.com/libffi/libffi/releases/download/v${VERSION}/libffi-${VERSION}.tar.gz"
SRC_DIR="libffi-${VERSION}"
PATCH_URI=""
PKG_NAMES="libffi8 libffi-devel"
BUILD_REQUIRES="dejagnu"
libffi8_CONTENTS="usr/bin/*-8.dll usr/share/doc/"
libffi_devel_CONTENTS="usr/include/ usr/lib/ usr/share/info/ usr/share/man/man3/"
KEEP_LA_FILES="none"

             reply	other threads:[~2022-10-04 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 18:11 Hannes Müller [this message]
     [not found] ` <93f7b9bc-43d1-00de-fca2-5ae762909022@dronecode.org.uk>
     [not found]   ` <f7d7240eacb93f4e33d25547bb29688d2d257934.camel@gmail.com>
2022-10-23 13:21     ` Jon Turney

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=23b4f0439c8123bffa09fda381929c216aaeeee0.camel@gmail.com \
    --to=h.c.f.mueller@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).