head	1.1;
access;
symbols
	pkgsrc-2026Q3:1.1.0.2;
locks; strict;
comment	@# @;


1.1
date	2026.09.27.10.34.45;	author tnn;	state Exp;
branches
	1.1.2.1;
next	;
commitid	8e1zYacCbKiqofXG;

1.1.2.1
date	2026.09.27.10.34.45;	author bsiegert;	state dead;
branches;
next	1.1.2.2;
commitid	98fypSo6iB43d4YG;

1.1.2.2
date	2026.10.03.19.37.16;	author bsiegert;	state Exp;
branches;
next	;
commitid	98fypSo6iB43d4YG;


desc
@@


1.1
log
@pcre2: fix broken symbol versioning test in configure

Recursive bump will likely be needed.
@
text
@$NetBSD$

Fix missing symbol versioning:

Don't let CONFIGURE_ENV override libtool's internal CP/MV/RM.
pkgsrc exports RM as "/bin/rm" but these tests really need "rm -f" because
of how they are written.

When creating a soname symlink the generated libtool runs
$RM "$linkname" && $LN_S "$realname" "$linkname"
which fails because $linkname does not exist yet.

PCRE2_CHECK_VSCRIPT links a shared library to probe for
-Wl,--version-script and the probe fails due to rm without -f even though
the link itself succeeded. Symbol versioning is then silently dropped and
configure says "with symbol versioning : n/a" rather than "yes".

The root cause is in libtool and a similar issue was reported
upstream in 2010:

https://lists.gnu.org/archive/html/bug-libtool/2010-03/msg00017.html

--- configure.orig	2026-08-31 13:49:04.000000000 +0000
+++ configure
@@@@ -6335,9 +6335,12 @@@@ max_cmd_len=$lt_cv_sys_max_cmd_len
 
 
 
-: ${CP="cp -f"}
-: ${MV="mv -f"}
-: ${RM="rm -f"}
+: ${CP="cp"}
+: ${MV="mv"}
+: ${RM="rm"}
+CP="${CP} -f"
+MV="${MV} -f"
+RM="${RM} -f"
 
 if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then
   lt_unset=unset
@


1.1.2.1
log
@file patch-configure was added on branch pkgsrc-2026Q3 on 2026-10-03 19:37:16 +0000
@
text
@d1 40
@


1.1.2.2
log
@Pullup ticket #7261 - requested by taca
devel/pcre2: build fix, security fix

Revisions pulled up:
- devel/pcre2/Makefile                                          1.33,1.35-1.36
- devel/pcre2/PLIST                                             1.14
- devel/pcre2/buildlink3.mk                                     1.9
- devel/pcre2/distinfo                                          1.30-1.32
- devel/pcre2/patches/patch-configure                           1.1

---
   Module Name:	pkgsrc
   Committed By:	tnn
   Date:		Sun Sep 27 10:34:46 UTC 2026

   Modified Files:
   	pkgsrc/devel/pcre2: Makefile buildlink3.mk distinfo
   Added Files:
   	pkgsrc/devel/pcre2/patches: patch-configure

   Log Message:
   pcre2: fix broken symbol versioning test in configure

   Recursive bump will likely be needed.

---
   Module Name:	pkgsrc
   Committed By:	wiz
   Date:		Tue Sep 29 05:55:04 UTC 2026

   Modified Files:
   	pkgsrc/devel/pcre2: Makefile distinfo

   Log Message:
   pcre2: update to 10.49.

   Version 10.49 28-September-2026
   -------------------------------

   1. (GHSA-r9hj-j2rw-4q3m) Security fix to prevent an out-of-bounds write with
   arbitrary data. Applications are only affected if using the
   pcre2_jit_stack_create() and pcre2_jit_stack_assign() APIs to provide a growable
   JIT stack, and then matching against a pattern with unusually high JIT stack
   usage, such as a large number of capturing groups.

   The implications of an out-of-bounds write could include arbitrary code
   execution.

   The issue is not a regression and affects releases 10.48 and earlier.
@
text
@a0 40
$NetBSD: patch-configure,v 1.1 2026/09/27 10:34:45 tnn Exp $

Fix missing symbol versioning:

Don't let CONFIGURE_ENV override libtool's internal CP/MV/RM.
pkgsrc exports RM as "/bin/rm" but these tests really need "rm -f" because
of how they are written.

When creating a soname symlink the generated libtool runs
$RM "$linkname" && $LN_S "$realname" "$linkname"
which fails because $linkname does not exist yet.

PCRE2_CHECK_VSCRIPT links a shared library to probe for
-Wl,--version-script and the probe fails due to rm without -f even though
the link itself succeeded. Symbol versioning is then silently dropped and
configure says "with symbol versioning : n/a" rather than "yes".

The root cause is in libtool and a similar issue was reported
upstream in 2010:

https://lists.gnu.org/archive/html/bug-libtool/2010-03/msg00017.html

--- configure.orig	2026-08-31 13:49:04.000000000 +0000
+++ configure
@@@@ -6335,9 +6335,12 @@@@ max_cmd_len=$lt_cv_sys_max_cmd_len
 
 
 
-: ${CP="cp -f"}
-: ${MV="mv -f"}
-: ${RM="rm -f"}
+: ${CP="cp"}
+: ${MV="mv"}
+: ${RM="rm"}
+CP="${CP} -f"
+MV="${MV} -f"
+RM="${RM} -f"
 
 if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then
   lt_unset=unset
@