From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libffi: Version bump. 3.4.8 -> 3.5.1
Date: Fri, 13 Jun 2025 15:49:42 +0200 [thread overview]
Message-ID: <20250613134942.3522060-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250611170347.44641-1-christian.melki@t2data.com>
Thanks, applied as 104105ce7e5260baa78a5b06f18046014255b8de.
Michael
[sent from post-receive hook]
On Fri, 13 Jun 2025 15:49:42 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Looks very minor.
> https://github.com/libffi/libffi/releases/tag/v3.5.0
> https://github.com/libffi/libffi/releases/tag/v3.5.1
>
> * License hash updated, copyright year change.
>
> * Forward patches, applies cleanly plus slight line offset adj.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250611170347.44641-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/libffi-3.4.8/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch b/patches/libffi-3.5.1/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> similarity index 89%
> rename from patches/libffi-3.4.8/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> rename to patches/libffi-3.5.1/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> index 9e6fcafdf8e0..0ed8cadaa3e7 100644
> --- a/patches/libffi-3.4.8/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> +++ b/patches/libffi-3.5.1/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> @@ -10,10 +10,10 @@ Signed-off-by: Christian Melki <christian.melki@t2data.com>
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile.am b/Makefile.am
> -index ba3d16626077..3f60163c75c9 100644
> +index cffcb9f6f5ed..386fb5444405 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> -@@ -35,7 +35,7 @@ MAKEOVERRIDES=
> +@@ -39,7 +39,7 @@ MAKEOVERRIDES=
> pkgconfigdir = $(libdir)/pkgconfig
> pkgconfig_DATA = libffi.pc
>
> diff --git a/patches/libffi-3.4.8/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch b/patches/libffi-3.5.1/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> similarity index 92%
> rename from patches/libffi-3.4.8/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> rename to patches/libffi-3.5.1/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> index 441b2cd48a89..60b1d5688d3a 100644
> --- a/patches/libffi-3.4.8/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> +++ b/patches/libffi-3.5.1/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> @@ -19,10 +19,10 @@ Signed-off-by: Ross Burton <ross.burton@intel.com>
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure.ac b/configure.ac
> -index f04789556ba4..630bdd555154 100644
> +index 258107d707ad..ef1a2852636e 100644
> --- a/configure.ac
> +++ b/configure.ac
> -@@ -402,7 +402,7 @@ AC_ARG_ENABLE(multi-os-directory,
> +@@ -403,7 +403,7 @@ AC_ARG_ENABLE(multi-os-directory,
>
> # These variables are only ever used when we cross-build to X86_WIN32.
> # And we only support this with GCC, so...
> diff --git a/patches/libffi-3.4.8/autogen.sh b/patches/libffi-3.5.1/autogen.sh
> similarity index 100%
> rename from patches/libffi-3.4.8/autogen.sh
> rename to patches/libffi-3.5.1/autogen.sh
> diff --git a/patches/libffi-3.4.8/series b/patches/libffi-3.5.1/series
> similarity index 100%
> rename from patches/libffi-3.4.8/series
> rename to patches/libffi-3.5.1/series
> diff --git a/rules/libffi.make b/rules/libffi.make
> index 923cb531db91..a94b7e963372 100644
> --- a/rules/libffi.make
> +++ b/rules/libffi.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBFFI) += libffi
> #
> # Paths and names
> #
> -LIBFFI_VERSION := 3.4.8
> -LIBFFI_MD5 := ba5fc49d57d13b9e6cecd0c78d76688b
> +LIBFFI_VERSION := 3.5.1
> +LIBFFI_MD5 := a67b82e7ec069f15cd81c23ced5049f4
> LIBFFI := libffi-$(LIBFFI_VERSION)
> LIBFFI_SUFFIX := tar.gz
> LIBFFI_SOURCE := $(SRCDIR)/$(LIBFFI).$(LIBFFI_SUFFIX)
> @@ -24,7 +24,7 @@ LIBFFI_DIR := $(BUILDDIR)/$(LIBFFI)
> LIBFFI_URL := https://github.com/libffi/libffi/releases/download/v$(LIBFFI_VERSION)/$(LIBFFI).$(LIBFFI_SUFFIX)
> LIBFFI_LICENSE := MIT
> LIBFFI_LICENSE_FILES := \
> - file://LICENSE;md5=1db54c9fd307a12218766c3c7f650ca7
> + file://LICENSE;md5=ce4763670c5b7756000561f9af1ab178
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2025-06-13 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 17:03 [ptxdist] [PATCH] " Christian Melki
2025-06-13 13:49 ` Michael Olbrich [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=20250613134942.3522060-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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