+ case "${usergroup_phase}" in + local run_cmd + run_cmd=run_su + shift + run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/gambc-4.9.7/work.log + su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/gambc-4.9.7/work.log => Checksum BLAKE2s OK for gambit-v4_9_7.tgz => Checksum SHA512 OK for gambit-v4_9_7.tgz ===> Installing dependencies for gambc-4.9.7 ========================================================================== The following variables will affect the build process of this package, gambc-4.9.7. Their current value is shown below: * CURSES_DEFAULT = ncurses Based on these variables, the following variables have been set: * CURSES_TYPE = ncurses * TERMCAP_TYPE = curses You may want to abort the process now with CTRL-C and change the value of variables in the first group before continuing. Be sure to run `/opt/pkg/bin/bmake clean' after the changes. ========================================================================== => Tool dependency gmake>=3.81: found gmake-4.4.1 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Full dependency pkg_install-info-[0-9]*: found pkg_install-info-4.5nb3 => Full dependency ncurses>=6.5: found ncurses-6.5nb1 ===> Overriding tools for gambc-4.9.7 ===> Extracting for gambc-4.9.7 ===> Patching for gambc-4.9.7 => Applying pkgsrc patches for gambc-4.9.7 => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-aa => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-aa Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aa,v 1.5 2023/04/26 20:53:23 nikita Exp $ | |Don't build the misc subdir. XXX: why? | |--- makefile.in.orig 2022-01-03 04:47:06.000000000 +0100 |+++ makefile.in 2023-04-26 22:00:35.624614777 +0200 -------------------------- Patching file makefile.in using Plan A... Hunk #1 succeeded at 80. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-bb => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-bb Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-bb,v 1.1 2023/04/30 19:32:30 nikita Exp $ | |https://salsa.debian.org/abdelq/gambc/-/blob/ca233c8bd3c8279e755e34287417aafe3c649629/debian/patches/reproducibility.patch | |Workaround for reproducibility issues | |--- doc/makefile.in |+++ doc/makefile.in -------------------------- Patching file doc/makefile.in using Plan A... Hunk #1 succeeded at 70. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- | |--- doc/texi2html |+++ doc/texi2html -------------------------- Patching file doc/texi2html using Plan A... Hunk #1 succeeded at 2520. Hunk #2 succeeded at 2543. Hunk #3 succeeded at 3137. Hunk #4 succeeded at 7413 (offset 10 lines). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-configure => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-configure Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-configure,v 1.1 2023/04/26 20:53:23 nikita Exp $ | |Fix portability. | |--- configure.orig 2023-04-26 22:07:06.196412552 +0200 |+++ configure 2023-04-26 22:14:22.126422238 +0200 -------------------------- Patching file configure using Plan A... Reversed (or previously applied) patch detected! Assuming -R.Hunk #1 succeeded at 17529 (offset 720 lines). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-contrib_GambitREPL_make-keys => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-contrib_GambitREPL_make-keys Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-contrib_GambitREPL_make-keys,v 1.1 2023/04/26 20:53:23 nikita Exp $ | |Fix portability. | |--- contrib/GambitREPL/make-keys.orig 2023-04-26 22:15:47.332909563 +0200 |+++ contrib/GambitREPL/make-keys 2023-04-26 22:16:36.834296594 +0200 -------------------------- Patching file contrib/GambitREPL/make-keys using Plan A... Hunk #1 succeeded at 33. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-misc_build-gambit-android => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-misc_build-gambit-android Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-misc_build-gambit-android,v 1.1 2023/04/26 20:53:23 nikita Exp $ | |Fix portability. | |--- misc/build-gambit-android.orig 2023-04-26 22:18:51.414207945 +0200 |+++ misc/build-gambit-android 2023-04-26 22:20:10.731378158 +0200 -------------------------- Patching file misc/build-gambit-android using Plan A... Hunk #1 succeeded at 111. Hunk #2 succeeded at 151. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-misc_build-gambit-iOS => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-misc_build-gambit-iOS Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-misc_build-gambit-iOS,v 1.1 2023/04/26 20:53:23 nikita Exp $ | |Fix portability. | |--- misc/build-gambit-iOS.orig 2023-04-26 22:19:02.324334524 +0200 |+++ misc/build-gambit-iOS 2023-04-26 22:21:44.927756847 +0200 -------------------------- Patching file misc/build-gambit-iOS using Plan A... Hunk #1 succeeded at 101. Hunk #2 succeeded at 141. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-misc_change-gvm-regs => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc/patches/patch-misc_change-gvm-regs Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-misc_change-gvm-regs,v 1.1 2023/04/26 20:53:23 nikita Exp $ | |Fix portability. | |--- misc/change-gvm-regs.orig 2023-04-26 22:19:15.917800254 +0200 |+++ misc/change-gvm-regs 2023-04-26 22:22:39.244105743 +0200 -------------------------- Patching file misc/change-gvm-regs using Plan A... Hunk #1 succeeded at 11. Hunk #2 succeeded at 23. done ===> Creating toolchain wrappers for gambc-4.9.7 ===> Configuring for gambc-4.9.7 => Preparing build-time and installation configuration. => putting flags first => Modifying GNU configure scripts to avoid --recheck => Replacing config-guess with pkgsrc versions => Replacing config-sub with pkgsrc versions => Replacing install-sh with pkgsrc version => Checking for portability problems in extracted files ERROR: [check-portability] => Found test ... == ...: ERROR: [check-portability] configure:17534: if test "$ENABLE_MARCH" == "no_enable_march"; then Explanation: =========================================================================== The "test" command, as well as the "[" command, are not required to know the "==" operator. Only a few implementations like bash and some versions of ksh support it. When you run "test foo == foo" on a platform that does not support the "==" operator, the result will be "false" instead of "true". This can lead to unexpected behavior. There are two ways to fix this error message. If the file that contains the "test ==" is needed for building the package, you should create a patch for it, replacing the "==" operator with "=". If the file is not needed, add its name to the CHECK_PORTABILITY_SKIP variable in the package Makefile. =========================================================================== *** Error code 1 Stop. bmake[1]: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc *** Error code 1 Stop. bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/lang/gambc