+ 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/gnustep-make-2.8.0nb1/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/gnustep-make-2.8.0nb1/work.log
=> Bootstrap dependency digest>=20211023: found digest-20220214
=> Checksum BLAKE2s OK for gnustep-make-2.8.0.tar.gz
=> Checksum SHA512 OK for gnustep-make-2.8.0.tar.gz
===> Installing dependencies for gnustep-make-2.8.0nb1
==========================================================================
The supported build options for gnustep-make are:

	fragile

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

	PKG_OPTIONS.gnustep (not defined)

==========================================================================
=> Tool dependency mktools-[0-9]*: found mktools-20220614
=> 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 clang-[0-9]*: found clang-16.0.6nb1
===> Overriding tools for gnustep-make-2.8.0nb1
===> Extracting for gnustep-make-2.8.0nb1
===> Patching for gnustep-make-2.8.0nb1
=> Applying pkgsrc patches for gnustep-make-2.8.0nb1
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-aa
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-aa
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aa,v 1.2 2006/01/12 18:36:22 joerg Exp $
|
|--- clean_os.sh.orig	Wed Mar  6 21:51:06 2002
|+++ clean_os.sh
--------------------------
Patching file clean_os.sh using Plan A...
Hunk #1 succeeded at 22.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-ab
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-ab
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ab,v 1.7 2020/04/16 09:21:51 manu Exp $
|
|--- config.make.in.orig	2020-04-05 16:59:54.000000000 +0200
|+++ config.make.in	2020-04-14 10:33:05.421958633 +0200
--------------------------
Patching file config.make.in using Plan A...
Hunk #1 succeeded at 153.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-ad
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-ad
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ad,v 1.12 2020/04/16 09:21:51 manu Exp $
|
|--- configure.orig	2020-04-05 16:59:54.000000000 +0200
|+++ configure	2020-04-14 10:31:20.723580801 +0200
--------------------------
Patching file configure using Plan A...
Hunk #1 succeeded at 3442.
Hunk #2 succeeded at 7462.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-ae
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-ae
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ae,v 1.10 2020/04/16 09:21:51 manu Exp $
|
|--- GNUmakefile.in.orig	2020-04-05 16:59:54.000000000 +0200
|+++ GNUmakefile.in	2020-04-14 10:31:20.761270469 +0200
--------------------------
Patching file GNUmakefile.in using Plan A...
Hunk #1 succeeded at 200.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-target.make
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make/patches/patch-target.make
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-target.make,v 1.1 2020/11/03 11:24:31 triaxx Exp $
|
|Prefer SUBST_VARS instead of SUBST_SED since mk/scripts/subst-identity.awk
|seems to be broken on FreeBSD.
|
|--- target.make.orig	2020-04-05 14:59:54.000000000 +0000
|+++ target.make
--------------------------
Patching file target.make using Plan A...
Hunk #1 succeeded at 591.
Hunk #2 succeeded at 624.
Hunk #3 succeeded at 642.
done
===> Creating toolchain wrappers for gnustep-make-2.8.0nb1
===> Configuring for gnustep-make-2.8.0nb1
=> Fixing man directory references.
=> Substituting "target" in target.make
=> 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
=> Replacing bash interpreter in bake_debian_files.sh.
INFO: [replace-interpreter] Nothing changed in bake_debian_files.sh.
=> Checking for portability problems in extracted files
checking build system type... x86_64-sun-solaris2.11
checking host system type... x86_64-sun-solaris2.11
checking target system type... x86_64-sun-solaris2.11
checking for pkgconfig... yes
checking for gnustep-config... no
checking for gawk... /usr/bin/nawk
checking for library combo... gnu-gnu-gnu
checking for x86_64-sun-solaris2.11-gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/pbulk/build/devel/gnustep-make/work/gnustep-make-2.8.0':
configure: error: C compiler cannot create executables
See `config.log' for more details
*** Error code 77

Stop.
bmake[1]: stopped in /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make
*** Error code 1

Stop.
bmake: stopped in /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/gnustep-make