+ 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-4.9.5/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent LUA_VERSION_REQD=54 WRKLOG=/tmp/bulklog/powerdns-4.9.5/work.log
=> Checksum BLAKE2s OK for pdns-4.9.5.tar.bz2
=> Checksum SHA512 OK for pdns-4.9.5.tar.bz2
===> Installing dependencies for powerdns-4.9.5
==========================================================================
The supported build options for powerdns are:

	botan sqlite zeromq

You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or the following variable.  Its current value is shown:

	PKG_OPTIONS.powerdns (not defined)

==========================================================================
==========================================================================
The following variables will affect the build process of this package,
powerdns-4.9.5.  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 ragel-[0-9]*: found ragel-6.10
=> Tool dependency libtool-base>=2.4.2nb9: found libtool-base-2.4.7nb1
=> Tool dependency bison>=1.0: found bison-3.8.2nb1
=> Tool dependency flex>=2.5.4a: found flex-2.6.4
=> Tool dependency m4>=1.4: found m4-1.4.19nb1
=> 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
=> Build dependency flex>=2.5.4a: found flex-2.6.4
=> Full dependency boost-libs-1.87.*: found boost-libs-1.87.0nb2
=> Full dependency boost-libs>=1.87.0: found boost-libs-1.87.0nb2
=> Full dependency curl>=8.13.0nb2: found curl-8.14.1
=> Full dependency lua54>=5.4.0<5.5: found lua54-5.4.7
=> Full dependency openssl>=3: found openssl-3.5.0
=> Full dependency gettext-lib>=0.22: found gettext-lib-0.22.5
=> Full dependency libiconv>=1.9.1: found libiconv-1.17
=> Full dependency libidn2>=2.0.0: found libidn2-2.3.7
=> Full dependency libunistring>=0.9.3: found libunistring-1.2
=> Full dependency libxml2>=2.6.2: found libxml2-2.14.4
=> Full dependency ncurses>=5.3nb1: found ncurses-6.5nb1
=> Full dependency nghttp2>=1.0.0: found nghttp2-1.66.0
=> Full dependency readline>=2.2: found readline-8.2nb2
=> Full dependency xz>=5.0.0: found xz-5.8.1
=> Full dependency zlib>=1.1.4: found zlib-1.3.1
===> Overriding tools for powerdns-4.9.5
===> Extracting for powerdns-4.9.5
===> Patching for powerdns-4.9.5
=> Applying pkgsrc patches for powerdns-4.9.5
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns/patches/patch-pdns_dnsscope.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns/patches/patch-pdns_dnsscope.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-pdns_dnsscope.cc,v 1.4 2025/06/30 11:00:50 jperkin Exp $
|
|Support IP_OFFMASK on illumos.
|
|--- pdns/dnsscope.cc.orig	2025-06-20 13:58:07.364067810 +0000
|+++ pdns/dnsscope.cc
--------------------------
Patching file pdns/dnsscope.cc using Plan A...
Hunk #1 succeeded at 45.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns/patches/patch-pdns_misc.hh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns/patches/patch-pdns_misc.hh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-pdns_misc.hh,v 1.3 2025/06/30 11:00:50 jperkin Exp $
|
|Checking for CLOCK_THREAD_CPUTIME_ID is sufficient, not all systems
|define _POSIX_THREAD_CPUTIME.
|
|--- pdns/misc.hh.orig	2025-06-20 13:40:32.920712323 +0000
|+++ pdns/misc.hh
--------------------------
Patching file pdns/misc.hh using Plan A...
Hunk #1 succeeded at 187.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns/patches/patch-pdns_qtype.hh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns/patches/patch-pdns_qtype.hh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-pdns_qtype.hh,v 1.3 2025/06/30 11:00:50 jperkin Exp $
|
|Avoid symbol pollution on SunOS.
|
|--- pdns/qtype.hh.orig	2025-06-20 14:11:31.859917271 +0000
|+++ pdns/qtype.hh
--------------------------
Patching file pdns/qtype.hh using Plan A...
Hunk #1 succeeded at 26.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns/patches/patch-pdns_version.cc
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/powerdns/patches/patch-pdns_version.cc
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-pdns_version.cc,v 1.3 2025/06/30 11:00:50 jperkin Exp $
|
|Do not store configure args, as they contain workdir references.
|
|--- pdns/version.cc.orig	2025-05-07 09:29:28.000000000 +0000
|+++ pdns/version.cc
--------------------------
Patching file pdns/version.cc using Plan A...
Hunk #1 succeeded at 160.
done
===> Creating toolchain wrappers for powerdns-4.9.5
/usr/bin/ln -s /home/pbulk/build/net/powerdns/work/.buildlink/lib/pkgconfig/lua-5.4.pc /home/pbulk/build/net/powerdns/work/.buildlink/lib/pkgconfig/lua.pc
===> Configuring for powerdns-4.9.5
=> 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:22202: if test "x$enable_fortify_source" == "xauto"

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:22207: if test "x$enable_fortify_source" == "x3"

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:22256: if test "x$enable_fortify_source" == "x2"

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:22305: if test "x$enable_fortify_source" == "x1"

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:27381: if test "x$PG_CONFIG" == "x"

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:27431: if test "x$PG_CONFIG" == "x"

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:31471: if test "x$enable_lto" == "xthin"

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:31521: if test "x$enable_lto" == "xauto"

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:31571: if test "x$enable_lto" == "xyes"

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
*** Error code 1

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