+ 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/db5-5.3.28nb2/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/db5-5.3.28nb2/work.log
=> Checksum BLAKE2s OK for db-5.3.28.tar.gz
=> Checksum SHA512 OK for db-5.3.28.tar.gz
===> Installing dependencies for db5-5.3.28nb2
=> Tool dependency libtool-base>=2.4.2nb9: found libtool-base-2.4.7nb1
=> Tool dependency pax>=20040802: found pax-20210219
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
===> Overriding tools for db5-5.3.28nb2
===> Extracting for db5-5.3.28nb2
===> Patching for db5-5.3.28nb2
=> Applying pkgsrc patches for db5-5.3.28nb2
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-aa
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-aa
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aa,v 1.4 2012/01/18 13:46:50 adam Exp $
|
|--- dist/Makefile.in.orig	2011-12-20 01:00:49.000000000 +0000
|+++ dist/Makefile.in
--------------------------
Patching file dist/Makefile.in using Plan A...
Hunk #1 succeeded at 17.
Hunk #2 succeeded at 54.
Hunk #3 succeeded at 73.
Hunk #4 succeeded at 92.
Hunk #5 succeeded at 157.
Hunk #6 succeeded at 175.
Hunk #7 succeeded at 1094 (offset 1 line).
Hunk #8 succeeded at 1109 (offset 1 line).
Hunk #9 succeeded at 1140 (offset 1 line).
Hunk #10 succeeded at 1163 (offset 1 line).
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-ab
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-ab
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ab,v 1.8 2019/02/19 15:18:19 hauke Exp $
|
|Fix bashisms.
|
|FreeBSD 10 is not FreeBSD 1.
|
|Add support for mutexes on aarch64 with GCC.
|
|--- dist/configure.orig	2013-09-09 15:35:02.000000000 +0000
|+++ dist/configure
--------------------------
Patching file dist/configure using Plan A...
Hunk #1 succeeded at 5112.
Hunk #2 succeeded at 6905.
Hunk #3 succeeded at 12227.
Hunk #4 succeeded at 13221.
Hunk #5 succeeded at 13232.
Hunk #6 succeeded at 15190.
Hunk #7 succeeded at 17054.
Hunk #8 succeeded at 17065.
Hunk #9 succeeded at 17712.
Hunk #10 succeeded at 18445.
Hunk #11 succeeded at 20565.
Hunk #12 succeeded at 21796.
Hunk #13 succeeded at 22149.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-ac
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-ac
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ac,v 1.2 2010/09/16 07:53:32 adam Exp $
|
|--- src/hmac/sha1.c.orig	2008-03-12 23:44:14.000000000 +0100
|+++ src/hmac/sha1.c
--------------------------
Patching file src/hmac/sha1.c using Plan A...
Hunk #1 succeeded at 101.
Hunk #2 succeeded at 190.
Hunk #3 succeeded at 208.
Hunk #4 succeeded at 236.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-dist_aclocal_libtool.m4
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-dist_aclocal_libtool.m4
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-dist_aclocal_libtool.m4,v 1.1 2014/04/22 14:42:35 asau Exp $
|
|--- dist/aclocal/libtool.m4.orig	2012-05-11 17:57:48.000000000 +0000
|+++ dist/aclocal/libtool.m4
--------------------------
Patching file dist/aclocal/libtool.m4 using Plan A...
Hunk #1 succeeded at 2406.
Hunk #2 succeeded at 2417.
Hunk #3 succeeded at 5110.
Hunk #4 succeeded at 6137.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-dist_config.bin
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-dist_config.bin
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-dist_config.bin,v 1.1 2019/02/19 15:18:19 hauke Exp $
|
|Add support for mutexes on aarch64 with GCC.
|
|--- dist/config.hin.orig	2010-04-12 20:25:23.000000000 +0000
|+++ dist/config.hin
--------------------------
Patching file dist/config.hin using Plan A...
Hunk #1 succeeded at 237 (offset 25 lines).
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_dbinc_atomic.h
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_dbinc_atomic.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_dbinc_atomic.h,v 1.2 2015/09/08 18:51:28 joerg Exp $
|
|Avoid 'definition of builtin function' error.
|
|--- src/dbinc/atomic.h.orig	2013-09-09 15:35:08.000000000 +0000
|+++ src/dbinc/atomic.h
--------------------------
Patching file src/dbinc/atomic.h using Plan A...
Hunk #1 succeeded at 70.
Hunk #2 succeeded at 144.
Hunk #3 succeeded at 176.
Hunk #4 succeeded at 206.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_dbinc_db.in
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_dbinc_db.in
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_dbinc_db.in,v 1.1 2016/08/26 17:23:16 joerg Exp $
|
|--- src/dbinc/db.in.orig	2016-08-26 13:25:32.335739127 +0000
|+++ src/dbinc/db.in
--------------------------
Patching file src/dbinc/db.in using Plan A...
Hunk #1 succeeded at 2782.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_dbinc_mutex_int.h
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_dbinc_mutex_int.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_dbinc_mutex_int.h,v 1.1 2019/02/19 15:18:19 hauke Exp $
|
|* adds support for mutexes on aarch64
|* fixes build failure on MIPS arch with -mips1.
|
|--- src/dbinc/mutex_int.h.orig	2010-04-12 20:25:22.000000000 +0000
|+++ src/dbinc/mutex_int.h
--------------------------
Patching file src/dbinc/mutex_int.h using Plan A...
Hunk #1 succeeded at 491.
Hunk #2 succeeded at 815.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mp_mp__fget.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mp_mp__fget.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_mp_mp__fget.c,v 1.1 2015/09/08 18:51:28 joerg Exp $
|
|--- src/mp/mp_fget.c.orig	2015-09-02 11:12:45.000000000 +0000
|+++ src/mp/mp_fget.c
--------------------------
Patching file src/mp/mp_fget.c using Plan A...
Hunk #1 succeeded at 649.
Hunk #2 succeeded at 955.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mp_mp__mvcc.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mp_mp__mvcc.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_mp_mp__mvcc.c,v 1.1 2015/09/08 18:51:28 joerg Exp $
|
|--- src/mp/mp_mvcc.c.orig	2015-09-02 11:12:47.000000000 +0000
|+++ src/mp/mp_mvcc.c
--------------------------
Patching file src/mp/mp_mvcc.c using Plan A...
Hunk #1 succeeded at 276.
Hunk #2 succeeded at 428.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mp_mp__region.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mp_mp__region.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_mp_mp__region.c,v 1.1 2015/09/08 18:51:28 joerg Exp $
|
|--- src/mp/mp_region.c.orig	2015-09-02 11:12:49.000000000 +0000
|+++ src/mp/mp_region.c
--------------------------
Patching file src/mp/mp_region.c using Plan A...
Hunk #1 succeeded at 245.
Hunk #2 succeeded at 302.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mutex_mut__method.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mutex_mut__method.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_mutex_mut__method.c,v 1.1 2015/09/08 18:51:28 joerg Exp $
|
|--- src/mutex/mut_method.c.orig	2015-09-02 11:12:53.000000000 +0000
|+++ src/mutex/mut_method.c
--------------------------
Patching file src/mutex/mut_method.c using Plan A...
Hunk #1 succeeded at 474.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mutex_mut__tas.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5/patches/patch-src_mutex_mut__tas.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_mutex_mut__tas.c,v 1.1 2015/09/08 18:51:28 joerg Exp $
|
|--- src/mutex/mut_tas.c.orig	2015-09-02 11:12:55.000000000 +0000
|+++ src/mutex/mut_tas.c
--------------------------
Patching file src/mutex/mut_tas.c using Plan A...
Hunk #1 succeeded at 47.
Hunk #2 succeeded at 536.
done
===> Creating toolchain wrappers for db5-5.3.28nb2
===> Configuring for db5-5.3.28nb2
=> 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] dist/validate/s_chk_message_id:32: if [ "$curnum" == "id" ]; 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] dist/validate/s_chk_message_id:47: if [ "$curnum" == "$lastnum" ]; 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: [check-portability] => Found test ... == ...:
ERROR: [check-portability] dist/validate/s_chk_message_id:48: if [ "$curnum" == "$rep_dup_msg_id" ]; 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/databases/db5
*** Error code 1

Stop.
bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/databases/db5