+ 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/fatback-1.3nb1/work.log + su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/fatback-1.3nb1/work.log WARNING: [license.mk] Every package should define a LICENSE. => Checksum BLAKE2s OK for fatback-1.3.tar.gz => Checksum SHA512 OK for fatback-1.3.tar.gz ===> Installing dependencies for fatback-1.3nb1 => Tool dependency flex>=2.5.4a: found flex-2.6.4 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Build dependency flex>=2.5.4a: found flex-2.6.4 => Full dependency pkg_install-info-[0-9]*: found pkg_install-info-4.5nb3 ===> Overriding tools for fatback-1.3nb1 ===> Extracting for fatback-1.3nb1 ===> Patching for fatback-1.3nb1 => Applying pkgsrc patches for fatback-1.3nb1 => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-aa => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-aa Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aa,v 1.3 2015/01/18 19:53:27 wiedi Exp $ | |--- output.c.orig 2001-05-30 15:47:04.000000000 +0000 |+++ output.c -------------------------- Patching file output.c using Plan A... Hunk #1 succeeded at 9. Hunk #2 succeeded at 57. Hunk #3 succeeded at 66. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-ab => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-ab Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ab,v 1.1.1.1 2005/05/25 10:29:01 agc Exp $ | |--- recovery.c 2005/05/25 10:11:56 1.1 |+++ recovery.c 2005/05/25 10:13:54 -------------------------- Patching file recovery.c using Plan A... Hunk #1 succeeded at 85. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-ac => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-ac Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ac,v 1.1 2006/10/09 13:23:37 joerg Exp $ | |--- vbr.c.orig 2006-10-09 15:14:51.000000000 +0000 |+++ vbr.c -------------------------- Patching file vbr.c using Plan A... Hunk #1 succeeded at 17. Hunk #2 succeeded at 49. Hunk #3 succeeded at 164. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-ad => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-ad Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ad,v 1.1 2006/10/09 13:23:37 joerg Exp $ | |--- sig.h.orig 2006-10-09 15:14:54.000000000 +0000 |+++ sig.h -------------------------- Patching file sig.h using Plan A... Hunk #1 succeeded at 4. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-ae => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-ae Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ae,v 1.1 2006/10/09 13:23:37 joerg Exp $ | |--- sig.c.orig 2006-10-09 15:14:56.000000000 +0000 |+++ sig.c -------------------------- Patching file sig.c using Plan A... Hunk #1 succeeded at 4. Hunk #2 succeeded at 15. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-af => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-af Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-af,v 1.1 2006/10/09 13:23:37 joerg Exp $ | |--- mbr.c.orig 2006-10-09 15:14:59.000000000 +0000 |+++ mbr.c -------------------------- Patching file mbr.c using Plan A... Hunk #1 succeeded at 37. Hunk #2 succeeded at 203. Hunk #3 succeeded at 282. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-cmd__cp.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback/patches/patch-cmd__cp.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-cmd__cp.c,v 1.1 2015/01/18 19:53:27 wiedi Exp $ | |Make sure NAME_MAX is defined. |Anything not too small should be ok, only used in a sanity check. |--- cmd_cp.c.orig 2001-05-30 15:40:00.000000000 +0000 |+++ cmd_cp.c -------------------------- Patching file cmd_cp.c using Plan A... Hunk #1 succeeded at 14. done ===> Creating toolchain wrappers for fatback-1.3nb1 ===> Configuring for fatback-1.3nb1 => 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 creating cache ./config.cache checking for a BSD compatible install... /opt/pkg/bin/bsdinstall -c -o pbulk -g pbulk checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal... found checking for working autoconf... found checking for working automake... found checking for working autoheader... found checking for working makeinfo... missing checking for c++... g++ checking whether the C++ compiler (g++ -pipe -O2 -msave-args -fno-aggressive-loop-optimizations -I/opt/pkg/include -L/opt/pkg/lib -Wl,-R/opt/pkg/lib) works... yes checking whether the C++ compiler (g++ -pipe -O2 -msave-args -fno-aggressive-loop-optimizations -I/opt/pkg/include -L/opt/pkg/lib -Wl,-R/opt/pkg/lib) is a cross-compiler... no checking whether we are using GNU C++... yes checking whether g++ accepts -g... yes checking for mawk... /usr/bin/nawk checking for bison... no checking for byacc... no checking for gcc... gcc checking whether the C compiler (gcc -pipe -O2 -msave-args -fno-aggressive-loop-optimizations -I/opt/pkg/include -L/opt/pkg/lib -Wl,-R/opt/pkg/lib) works... no configure: error: installation or configuration problem: C compiler cannot create executables. *** Error code 1 Stop. bmake[1]: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback *** Error code 1 Stop. bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/sysutils/fatback