+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent LUA_VERSION_REQD=54 WRKLOG=/tmp/bulklog/powerdns-recursor-4.9.9/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent LUA_VERSION_REQD=54 WRKLOG=/tmp/bulklog/powerdns-recursor-4.9.9/work.log
=> Checksum BLAKE2s OK for pdns-recursor-4.9.9.tar.bz2
=> Checksum SHA512 OK for pdns-recursor-4.9.9.tar.bz2
===> Installing dependencies for powerdns-recursor-4.9.9
==========================================================================
The following variables will affect the build process of this package,
powerdns-recursor-4.9.9.  Their current value is shown below:

        * CURSES_DEFAULT = ncurses
        * LUA_VERSION_DEFAULT = 54
        * READLINE_DEFAULT = readline
        * SSLBASE (defined)
        * SSLCERTBUNDLE (not defined)
        * SSLCERTS = /etc/opt/pkg/openssl/certs
        * SSLDIR = /etc/opt/pkg/openssl
        * SSLKEYS = /etc/opt/pkg/openssl/private

Based on these variables, the following variables have been set:

        * CURSES_TYPE = ncurses
        * LUA_PACKAGE = lua54
        * READLINE_TYPE = readline
        * 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 pkgconf-[0-9]*: found pkgconf-2.4.3nb1
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency boost-headers-1.87.*: found boost-headers-1.87.0nb3
=> Full dependency lua54>=5.4.0<5.5: found lua54-5.4.7
=> Full dependency openssl>=3: found openssl-3.5.0
=> Full dependency ncurses>=5.3nb1: found ncurses-6.5nb1
=> Full dependency readline>=2.2: found readline-8.2nb2
===> Overriding tools for powerdns-recursor-4.9.9
===> Extracting for powerdns-recursor-4.9.9
===> Patching for powerdns-recursor-4.9.9
=> Applying pkgsrc patches for powerdns-recursor-4.9.9
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns-recursor/patches/patch-dns.hh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns-recursor/patches/patch-dns.hh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-dns.hh,v 1.4 2025/06/30 11:06:46 jperkin Exp $
|
|Only attempt to define byte order if unset.
|
|--- dns.hh.orig	2024-09-17 08:11:58.000000000 +0000
|+++ dns.hh
--------------------------
Patching file dns.hh using Plan A...
Hunk #1 succeeded at 120.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns-recursor/patches/patch-ext_json11_json11.cpp
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns-recursor/patches/patch-ext_json11_json11.cpp
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ext_json11_json11.cpp,v 1.1 2017/05/22 23:41:52 joerg Exp $
|
|Clang rejects ordering relations for nullptr, so introduce a template
|indirection.
|
|--- ext/json11/json11.cpp.orig	2017-01-13 08:55:55.000000000 +0000
|+++ ext/json11/json11.cpp
--------------------------
Patching file ext/json11/json11.cpp using Plan A...
Hunk #1 succeeded at 146 (offset 14 lines).
Hunk #2 succeeded at 171 (offset 14 lines).
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns-recursor/patches/patch-qtype.hh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns-recursor/patches/patch-qtype.hh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-qtype.hh,v 1.2 2022/09/29 12:47:31 jperkin Exp $
|
|Avoid symbol pollution on SunOS.
|
|--- qtype.hh.orig	2022-09-19 10:31:34.000000000 +0000
|+++ qtype.hh
--------------------------
Patching file qtype.hh using Plan A...
Hunk #1 succeeded at 26.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns-recursor/patches/patch-version.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns-recursor/patches/patch-version.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-version.cc,v 1.3 2025/06/30 11:06:46 jperkin Exp $
|
|Do not store configure args, as they contain workdir references.
|
|--- version.cc.orig	2025-06-23 11:49:15.710023097 +0000
|+++ version.cc
--------------------------
Patching file version.cc using Plan A...
Hunk #1 succeeded at 155.
done
===> Creating toolchain wrappers for powerdns-recursor-4.9.9
/usr/bin/ln -s /home/pbulk/build/net/powerdns-recursor/work/.buildlink/lib/pkgconfig/lua-5.4.pc /home/pbulk/build/net/powerdns-recursor/work/.buildlink/lib/pkgconfig/lua.pc
===> Configuring for powerdns-recursor-4.9.9
=> 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:25975: if test "x$enable_fortify_source" == "xauto"; 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] configure:25979: if test "x$enable_fortify_source" == "x3"; 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] configure:26024: if test "x$enable_fortify_source" == "x2"; 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] configure:26069: if test "x$enable_fortify_source" == "x1"; 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] configure:26728: if test "x$enable_lto" == "xthin"; 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] configure:26774: if test "x$enable_lto" == "xauto"; 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] configure:26820: if test "x$enable_lto" == "xyes"; 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/net/powerdns-recursor
*** Error code 1

Stop.
bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns-recursor