Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
To: Peter Seiderer <ps.report@gmx.net>, buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH v1] package/pcre2: bump version to 10.44
Date: Thu, 9 Jan 2025 12:54:11 +0100	[thread overview]
Message-ID: <0560e329-4abe-4988-9fa3-bb4ddc733773@bubu1.eu> (raw)
In-Reply-To: <20240626090026.31083-1-ps.report@gmx.net>

Hi,

On 26.06.24 11:00, Peter Seiderer via buildroot wrote:
> - enable PCRE2_AUTORECONF to fix the following buildi/relink failure:
> 
>      x86_64-buildroot-linux-gnu-gcc: ERROR: unsafe header/library path used
>      in cross-compilation: '-L/usr/lib'
> 
> For details see [1].
> 
> [1] https://github.com/PCRE2Project/pcre2/blob/master/ChangeLog
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>

Not sure why this slipped through the cracks, but FWIW:

Tested-by: Marcus Hoffmann <buildroot@bubu1.eu>

> ---
>   package/pcre2/pcre2.hash | 4 ++--
>   package/pcre2/pcre2.mk   | 5 ++++-
>   2 files changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/package/pcre2/pcre2.hash b/package/pcre2/pcre2.hash
> index f2e17df753..8b22040ba7 100644
> --- a/package/pcre2/pcre2.hash
> +++ b/package/pcre2/pcre2.hash
> @@ -1,5 +1,5 @@
>   # Locally calculated after checking pgp signature:
> -# https://github.com/PhilipHazel/pcre2/releases/download/pcre2-10.43/pcre2-10.43.tar.bz2.sig
> -sha256  e2a53984ff0b07dfdb5ae4486bbb9b21cca8e7df2434096cc9bf1b728c350bcb  pcre2-10.43.tar.bz2
> +# https://github.com/PhilipHazel/pcre2/releases/download/pcre2-10.44/pcre2-10.44.tar.bz2.sig
> +sha256  d34f02e113cf7193a1ebf2770d3ac527088d485d4e047ed10e5d217c6ef5de96  pcre2-10.44.tar.bz2
>   # Locally computed
>   sha256  030087e2e8dd7c1bdd26057d25d4ded8f45bbf01ad458d68665ad04b8b0fbedf  LICENCE
> diff --git a/package/pcre2/pcre2.mk b/package/pcre2/pcre2.mk
> index 9641f22e81..191596181a 100644
> --- a/package/pcre2/pcre2.mk
> +++ b/package/pcre2/pcre2.mk
> @@ -4,7 +4,7 @@
>   #
>   ################################################################################
>   
> -PCRE2_VERSION = 10.43
> +PCRE2_VERSION = 10.44
>   PCRE2_SITE = https://github.com/PCRE2Project/pcre2/releases/download/pcre2-$(PCRE2_VERSION)
>   PCRE2_SOURCE = pcre2-$(PCRE2_VERSION).tar.bz2
>   PCRE2_LICENSE = BSD-3-Clause
> @@ -12,6 +12,9 @@ PCRE2_LICENSE_FILES = LICENCE
>   PCRE2_CPE_ID_VENDOR = pcre
>   PCRE2_INSTALL_STAGING = YES
>   PCRE2_CONFIG_SCRIPTS = pcre2-config
> +# Fixes build/relink failure ("ERROR: unsafe header/library path used in
> +# cross-compilation: '-L/usr/lib'")
> +PCRE2_AUTORECONF = YES
>   
>   PCRE2_CONF_OPTS += --enable-pcre2-8
>   PCRE2_CONF_OPTS += $(if $(BR2_PACKAGE_PCRE2_16),--enable-pcre2-16,--disable-pcre2-16)

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-01-09 12:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  9:00 [Buildroot] [PATCH v1] package/pcre2: bump version to 10.44 Peter Seiderer via buildroot
2025-01-09 11:54 ` Marcus Hoffmann via buildroot [this message]
2025-02-04 17:18 ` Thomas Petazzoni via buildroot
2025-02-04 17:18   ` Thomas Petazzoni

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=0560e329-4abe-4988-9fa3-bb4ddc733773@bubu1.eu \
    --to=buildroot@buildroot.org \
    --cc=buildroot@bubu1.eu \
    --cc=buildroot@busybox.net \
    --cc=ps.report@gmx.net \
    /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