+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /usr/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/flow-tools-0.68nb13/work.log
+ su pbulk -c '"$@"' make /usr/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/flow-tools-0.68nb13/work.log
=> Bootstrap dependency digest>=20211023: found digest-20220214
WARNING: [license.mk] Every package should define a LICENSE.
=> Checksum BLAKE2s OK for flow-tools-0.68.tar.gz
=> Checksum SHA512 OK for flow-tools-0.68.tar.gz
===> Installing dependencies for flow-tools-0.68nb13
==========================================================================
The supported build options for flow-tools are:

	mysql pgsql python

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

	PKG_OPTIONS.flow-tools (not defined)

==========================================================================
=> Tool dependency mktools-[0-9]*: found mktools-20220614
=> Tool dependency flex>=2.5.4a: found flex-2.6.4
=> Tool dependency nbpatch-[0-9]*: found nbpatch-20151107
=> 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 tcp_wrappers>=7.6.1nb3: found tcp_wrappers-7.6.4nb2
=> Full dependency zlib>=1.2.3: found zlib-1.3.1
===> Overriding tools for flow-tools-0.68nb13
===> Extracting for flow-tools-0.68nb13
===> Patching for flow-tools-0.68nb13
=> Applying pkgsrc patches for flow-tools-0.68nb13
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-aa
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-aa
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aa,v 1.3 2004/04/22 15:33:35 seb Exp $
|
|--- configs/Makefile.am.orig	2003-11-25 07:01:37.000000000 +0000
|+++ configs/Makefile.am
--------------------------
Patching file configs/Makefile.am using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ab
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ab
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ab,v 1.4 2005/06/23 14:20:56 seb Exp $
|
|--- configs/Makefile.in.orig	2005-06-21 23:24:13.000000000 +0000
|+++ configs/Makefile.in
--------------------------
Patching file configs/Makefile.in using Plan A...
Hunk #1 succeeded at 88.
Hunk #2 succeeded at 110.
Hunk #3 succeeded at 180.
Hunk #4 succeeded at 222.
Hunk #5 succeeded at 240.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ac
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ac
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ac,v 1.3 2005/06/23 14:20:56 seb Exp $
|
|--- docs/Makefile.am.orig	2005-05-11 00:26:20.000000000 +0000
|+++ docs/Makefile.am
--------------------------
Patching file docs/Makefile.am using Plan A...
Hunk #1 succeeded at 1.
Hunk #2 succeeded at 23.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ad
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ad
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ad,v 1.4 2005/06/23 14:20:56 seb Exp $
|
|--- docs/Makefile.in.orig	2005-05-11 14:20:18.000000000 +0000
|+++ docs/Makefile.in
--------------------------
Patching file docs/Makefile.in using Plan A...
Hunk #1 succeeded at 90.
Hunk #2 succeeded at 111.
Hunk #3 succeeded at 132.
Hunk #4 succeeded at 346.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ae
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ae
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ae,v 1.2 2003/05/23 07:19:43 seb Exp $
|
|--- lib/Makefile.am.orig	2003-03-12 03:31:23.000000000 +0000
|+++ lib/Makefile.am
--------------------------
Patching file lib/Makefile.am using Plan A...
Hunk #1 succeeded at 6.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-af
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-af
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-af,v 1.4 2005/06/23 14:20:56 seb Exp $
|
|--- lib/Makefile.in.orig	2005-06-21 23:24:04.000000000 +0000
|+++ lib/Makefile.in
--------------------------
Patching file lib/Makefile.in using Plan A...
Hunk #1 succeeded at 95.
Hunk #2 succeeded at 148.
Hunk #3 succeeded at 270.
Hunk #4 succeeded at 355.
Hunk #5 succeeded at 398.
Hunk #6 succeeded at 416.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ag
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ag
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ag,v 1.3 2004/04/22 15:33:35 seb Exp $
|
|--- lib/ftpaths.h.in.orig	2003-11-11 16:49:14.000000000 +0000
|+++ lib/ftpaths.h.in
--------------------------
Patching file lib/ftpaths.h.in using Plan A...
Hunk #1 succeeded at 29.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ah
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ah
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ah,v 1.5 2013/02/03 17:48:45 kefren Exp $
|
|--- src/flow-capture.c.orig	2004-01-05 19:56:50.000000000 +0200
|+++ src/flow-capture.c	2013-02-03 18:33:26.000000000 +0200
--------------------------
Patching file src/flow-capture.c using Plan A...
Hunk #1 succeeded at 350.
Hunk #2 succeeded at 451.
Hunk #3 succeeded at 999.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ai
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ai
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ai,v 1.3 2013/10/13 21:52:44 sbd Exp $
|
|--- src/flow-dscan.c.orig	2003-04-02 18:03:01.000000000 +0000
|+++ src/flow-dscan.c
--------------------------
Patching file src/flow-dscan.c using Plan A...
Hunk #1 succeeded at 112.
Hunk #2 succeeded at 234.
Hunk #3 succeeded at 455.
Hunk #4 succeeded at 482.
Hunk #5 succeeded at 1005.
Hunk #6 succeeded at 1013.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-aj
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-aj
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aj,v 1.2 2003/05/23 07:19:44 seb Exp $
|
|--- src/flow-fanout.c.orig	2003-04-04 02:24:40.000000000 +0000
|+++ src/flow-fanout.c
--------------------------
Patching file src/flow-fanout.c using Plan A...
Hunk #1 succeeded at 302 (offset 15 lines).
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ak
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ak
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ak,v 1.3 2005/06/23 14:20:56 seb Exp $
|
|--- src/flow-export.c.orig	2004-03-31 03:11:14.000000000 +0000
|+++ src/flow-export.c
--------------------------
Patching file src/flow-export.c using Plan A...
Hunk #1 succeeded at 865.
Hunk #2 succeeded at 892.
Hunk #3 succeeded at 1200.
Hunk #4 succeeded at 1258.
Hunk #5 succeeded at 1376.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-al
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-al
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-al,v 1.1 2005/06/23 14:20:56 seb Exp $
|
|--- Makefile.am.orig	2005-05-11 14:13:44.000000000 +0000
|+++ Makefile.am
--------------------------
Patching file Makefile.am using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-am
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-am
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-am,v 1.1 2005/06/23 14:20:56 seb Exp $
|
|--- Makefile.in.orig	2005-06-23 12:43:35.000000000 +0000
|+++ Makefile.in
--------------------------
Patching file Makefile.in using Plan A...
Hunk #1 succeeded at 88.
Hunk #2 succeeded at 98.
Hunk #3 succeeded at 118.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-an
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-an
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-an,v 1.1 2006/02/24 20:32:19 joerg Exp $
|
|--- src/flow-header.c.orig	2006-02-24 20:29:49.000000000 +0000
|+++ src/flow-header.c
--------------------------
Patching file src/flow-header.c using Plan A...
Hunk #1 succeeded at 32.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ao
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ao
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ao,v 1.1 2013/02/03 17:48:45 kefren Exp $
|
|--- lib/ftlib.h.orig	2013-02-03 18:49:10.000000000 +0200
|+++ lib/ftlib.h	2013-02-03 18:32:09.000000000 +0200
--------------------------
Patching file lib/ftlib.h using Plan A...
Hunk #1 succeeded at 2710.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ap
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ap
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ap,v 1.1 2013/02/03 17:48:45 kefren Exp $
|
|--- lib/ftfile.c.orig	2013-02-03 18:48:54.000000000 +0200
|+++ lib/ftfile.c	2013-02-03 18:32:58.000000000 +0200
--------------------------
Patching file lib/ftfile.c using Plan A...
Hunk #1 succeeded at 410.
Hunk #2 succeeded at 418.
Hunk #3 succeeded at 499.
Hunk #4 succeeded at 512.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ar
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-ar
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ar,v 1.1 2006/07/18 11:06:48 seb Exp $
|
|--- lib/ftchash.c.orig	2003-08-12 18:04:25.000000000 +0000
|+++ lib/ftchash.c
--------------------------
Patching file lib/ftchash.c using Plan A...
Hunk #1 succeeded at 326.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-as
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-as
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-as,v 1.2 2013/10/13 21:52:44 sbd Exp $
|
|--- lib/ftio.c.orig	2003-02-24 00:51:47.000000000 +0000
|+++ lib/ftio.c
--------------------------
Patching file lib/ftio.c using Plan A...
Hunk #1 succeeded at 1605.
Hunk #2 succeeded at 1640.
Hunk #3 succeeded at 2272.
Hunk #4 succeeded at 2297.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-at
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-at
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-at,v 1.1 2006/07/18 11:06:48 seb Exp $
|
|--- lib/fttlv.c.orig	2003-02-13 02:38:43.000000000 +0000
|+++ lib/fttlv.c
--------------------------
Patching file lib/fttlv.c using Plan A...
Hunk #1 succeeded at 68.
Hunk #2 succeeded at 107.
Hunk #3 succeeded at 145.
Hunk #4 succeeded at 183.
Hunk #5 succeeded at 230.
Hunk #6 succeeded at 287.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-lib_ftfil.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-lib_ftfil.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-lib_ftfil.c,v 1.1 2012/11/19 02:58:12 joerg Exp $
|
|--- lib/ftfil.c.orig	2012-11-19 00:45:30.000000000 +0000
|+++ lib/ftfil.c
--------------------------
Patching file lib/ftfil.c using Plan A...
Hunk #1 succeeded at 76.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-lib_ftstat.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-lib_ftstat.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-lib_ftstat.c,v 1.1 2013/10/13 21:52:44 sbd Exp $
|
|--- lib/ftstat.c.orig	2005-05-10 15:48:12.000000000 +0000
|+++ lib/ftstat.c
--------------------------
Patching file lib/ftstat.c using Plan A...
Hunk #1 succeeded at 12363.
Hunk #2 succeeded at 12619.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-src_flow-print.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/net/flow-tools/patches/patch-src_flow-print.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_flow-print.c,v 1.1 2013/10/13 21:52:44 sbd Exp $
|
|--- src/flow-print.c.orig	2003-04-02 18:03:02.000000000 +0000
|+++ src/flow-print.c
--------------------------
Patching file src/flow-print.c using Plan A...
Hunk #1 succeeded at 298.
Hunk #2 succeeded at 352.
Hunk #3 succeeded at 401.
Hunk #4 succeeded at 469.
Hunk #5 succeeded at 681.
Hunk #6 succeeded at 718.
Hunk #7 succeeded at 2182.
Hunk #8 succeeded at 2249.
done
===> Creating toolchain wrappers for flow-tools-0.68nb13
===> Configuring for flow-tools-0.68nb13
=> 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 a BSD-compatible install... /bin/install -c -o pbulk -g pbulk
checking whether build environment is sane... yes
checking for gawk... /bin/gawk
checking whether make sets $(MAKE)... yes
checking for x86_64-redhat-linux-gcc... cc
checking for C compiler default output... 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 cc accepts -g... yes
checking for cc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of cc... gcc3
checking for a BSD-compatible install... /bin/install -c -o pbulk -g pbulk
checking whether make sets $(MAKE)... (cached) yes
checking for bison... no
checking for byacc... no
checking for x86_64-redhat-linux-ranlib... no
checking for ranlib... ranlib
checking for flex... /usr/pkg/bin/flex
checking for yywrap in -lfl... no
checking for yywrap in -ll... no
checking lex output file root... lex.yy
checking whether yytext is a pointer... no
checking for main in -ly... no
checking for zlibVersion in -lz... yes
checking for allow_severity in -lwrap... no
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking how to run the C preprocessor... cc -E
checking for egrep... 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 fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking features.h usability... yes
checking features.h presence... yes
checking for features.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for unistd.h... (cached) yes
checking for sin_len in sockaddr_in ... 
no
checking for an ANSI C-conforming const... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for struct stat.st_rdev... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking for working alloca.h... yes
checking for alloca... yes
checking return type of signal handlers... void
checking for gethostbyname in -lnsl... no
checking for socket in -lsocket... no
checking for gethostname... yes
checking for gettimeofday... yes
checking for select... yes
checking for socket... yes
checking for strdup... yes
checking for strtoul... yes
checking for timelocal... yes
checking for sigaction... yes
checking for strsep... yes
checking for strerror... yes
checking for strtoull... yes
checking strtoul returns 64 bits... yes
configure: creating ./config.status
config.status: creating lib/Makefile
config.status: creating src/Makefile
config.status: creating bin/Makefile
config.status: creating Makefile
config.status: creating docs/Makefile
config.status: creating lib/ftpaths.h
config.status: creating configs/Makefile
config.status: creating docs/flow-capture.1
config.status: creating docs/flow-capture.html
config.status: creating docs/flow-nfilter.1
config.status: creating docs/flow-nfilter.html
config.status: creating docs/flow-print.1
config.status: creating docs/flow-print.html
config.status: creating docs/flow-report.1
config.status: creating docs/flow-report.html
config.status: creating docs/flow-receive.1
config.status: creating docs/flow-receive.html
config.status: creating docs/flow-tag.1
config.status: creating docs/flow-tag.html
config.status: creating docs/flow-mask.1
config.status: creating docs/flow-mask.html
config.status: creating docs/flow-fanout.1
config.status: creating docs/flow-fanout.html
config.status: creating docs/flow-xlate.1
config.status: creating docs/flow-xlate.html
config.status: creating docs/flow-rpt2rrd.1
config.status: creating docs/flow-rpt2rrd.html
config.status: creating docs/flow-rptfmt.1
config.status: creating docs/flow-rptfmt.html
config.status: creating docs/flow-log2rrd.1
config.status: creating docs/flow-log2rrd.html
config.status: creating lib/ftconfig.h
config.status: executing depfiles commands

Please subscribe to the flow-tools mailing list by sending a message to
flow-tools-request@splintered.net

Now type make to continue the build process