+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/local/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/pam-fprint-0.2nb2/work.log
+ su pbulk -c '"$@"' make /opt/local/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/pam-fprint-0.2nb2/work.log
=> Bootstrap dependency digest>=20211023: found digest-20211023
=> Checksum BLAKE2s OK for pam_fprint-0.2.tar.bz2
=> Checksum SHA512 OK for pam_fprint-0.2.tar.bz2
===> Installing dependencies for pam-fprint-0.2nb2
==========================================================================
The following variables will affect the build process of this package,
pam-fprint-0.2nb2.  Their current value is shown below:

        * PAM_DEFAULT = solaris-pam

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

        * PAMBASE (defined, but empty)

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/local/bin/bmake clean' after the changes.
==========================================================================
=> Tool dependency gmake>=3.81: found gmake-4.3nb3
=> Tool dependency pkgconf-[0-9]*: found pkgconf-1.8.0
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency gcc10>=10.4.0: found gcc10-10.4.0
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency libfprint>=0.7.0: found libfprint-0.7.0nb27
=> Full dependency gcc10-libs>=10.4.0: found gcc10-libs-10.4.0
===> Overriding tools for pam-fprint-0.2nb2
===> Extracting for pam-fprint-0.2nb2
===> Patching for pam-fprint-0.2nb2
=> Applying pkgsrc patches for pam-fprint-0.2nb2
=> Verifying /data/jenkins/workspace/pkgsrc-2021Q4-x86_64/security/pam-fprint/patches/patch-aa
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-2021Q4-x86_64/security/pam-fprint/patches/patch-aa
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aa,v 1.1.1.1 2009/02/26 21:52:00 plunky Exp $
|
|- pamtest relies on libpam_misc so disable it
|- pam modules directory is hardcoded, fix that
|
|--- src/Makefile.in.orig	2007-11-19 19:15:11.000000000 +0000
|+++ src/Makefile.in
--------------------------
Patching file src/Makefile.in using Plan A...
Hunk #1 succeeded at 30.
Hunk #2 succeeded at 163.
done
=> Verifying /data/jenkins/workspace/pkgsrc-2021Q4-x86_64/security/pam-fprint/patches/patch-src_pam__fprint__enroll.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-2021Q4-x86_64/security/pam-fprint/patches/patch-src_pam__fprint__enroll.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_pam__fprint__enroll.c,v 1.1 2012/11/23 12:30:01 joerg Exp $
|
|--- src/pam_fprint_enroll.c.orig	2012-11-22 21:39:34.000000000 +0000
|+++ src/pam_fprint_enroll.c
--------------------------
Patching file src/pam_fprint_enroll.c using Plan A...
Hunk #1 succeeded at 47.
done
=> Verifying /data/jenkins/workspace/pkgsrc-2021Q4-x86_64/security/pam-fprint/patches/patch-src_pam__fprint.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-2021Q4-x86_64/security/pam-fprint/patches/patch-src_pam__fprint.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_pam__fprint.c,v 1.1 2012/11/23 12:30:01 joerg Exp $
|
|--- src/pam_fprint.c.orig	2012-11-22 21:40:14.000000000 +0000
|+++ src/pam_fprint.c
--------------------------
Patching file src/pam_fprint.c using Plan A...
Hunk #1 succeeded at 21.
Hunk #2 succeeded at 43.
Hunk #3 succeeded at 64.
Hunk #4 succeeded at 99.
done
===> Creating toolchain wrappers for pam-fprint-0.2nb2
===> Configuring for pam-fprint-0.2nb2
=> 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
checking for a BSD-compatible install... /opt/local/bin/bsdinstall -c -o pbulk -g pbulk
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... /opt/local/bin/nawk
checking whether make sets $(MAKE)... yes
checking for x86_64-sun-solaris2.11-gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... (cached) /usr/xpg4/bin/grep
checking for egrep... (cached) /usr/xpg4/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking security/pam_modules.h usability... no
checking security/pam_modules.h presence... yes
configure: WARNING: security/pam_modules.h: present but cannot be compiled
configure: WARNING: security/pam_modules.h:     check for missing prerequisite headers?
configure: WARNING: security/pam_modules.h: see the Autoconf documentation
configure: WARNING: security/pam_modules.h:     section "Present But Cannot Be Compiled"
configure: WARNING: security/pam_modules.h: proceeding with the preprocessor's result
configure: WARNING: security/pam_modules.h: in the future, the compiler will take precedence
checking for security/pam_modules.h... yes
checking for pam_start in -lpam... yes
checking pkg-config is at least version 0.9.0... yes
checking for FPRINT... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: executing depfiles commands