CVS commit: pkgsrc/databases/py-duckdb

Module Name:	pkgsrc
Committed By:	jperkin
Date:		Thu Aug 13 07:14:39 UTC 2026

Modified Files:
	pkgsrc/databases/py-duckdb: Makefile

Log Message:
py-duckdb: Pass CMAKE_BUILD_PARALLEL_LEVEL.

Any package that uses py-scikit-build-core to build does not honour MAKE_JOBS.
Some packages use make and so are single threaded, but some like duckdb use
ninja, and that defaults to ncores+2(!) per build.

On my 72-core build host, building 3 py-duckdb packages simultaneously, this is
enough to completely swamp things and cause knock-on failures that effectively
kill the bulk build.

Ideally this needs to be done in a build.mk or similar for py-scikit-build-core
but this gets us past this for now.


To generate a diff of this commit:
cvs rdiff -u -r1.9 -r1.10 pkgsrc/databases/py-duckdb/Makefile

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: pkgsrc/databases/py-duckdb/Makefile
diff -u pkgsrc/databases/py-duckdb/Makefile:1.9 pkgsrc/databases/py-duckdb/Makefile:1.10
--- pkgsrc/databases/py-duckdb/Makefile:1.9	Wed Aug 12 03:52:35 2026
+++ pkgsrc/databases/py-duckdb/Makefile	Thu Aug 13 07:14:39 2026
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.9 2026/08/12 03:52:35 ryoon Exp $
+# $NetBSD: Makefile,v 1.10 2026/08/13 07:14:39 jperkin Exp $
 
 DISTNAME=	duckdb-1.5.5
 PKGNAME=	${PYPKGPREFIX}-${DISTNAME}
@@ -25,6 +25,10 @@ PYTHON_VERSIONS_INCOMPATIBLE=	310 311
 
 WHEEL_ARGS+=	-C skbuild.build-dir=${WRKDIR}/build
 
+# XXX: Belongs in py-scikit-build-core/build.mk or similar as this affects
+# all its dependents, but duckdb is by far the worst offender.
+MAKE_ENV+=	CMAKE_BUILD_PARALLEL_LEVEL=${MAKE_JOBS:U1}
+
 post-patch:
 	${MKDIR} ${WRKSRC}/build