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

        * PYTHON_VERSION_DEFAULT = 312

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

        * PYPACKAGE = python27

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
`/usr/pkg/bin/bmake clean' after the changes.
==========================================================================
=> Tool dependency python27>=2.7: found python27-2.7.18nb19
=> Tool dependency mktools-[0-9]*: found mktools-20220614
=> Tool dependency nbpatch-[0-9]*: found nbpatch-20151107
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
===> Overriding tools for botan-1.10.17nb2
===> Extracting for botan-1.10.17nb2
===> Patching for botan-1.10.17nb2
=> Applying pkgsrc patches for botan-1.10.17nb2
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_build-data_arch_arm.txt
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_build-data_arch_arm.txt
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_build-data_arch_arm.txt,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/build-data/arch/arm.txt.orig	2016-02-03 07:57:06.000000000 +0000
|+++ src/build-data/arch/arm.txt
--------------------------
Patching file src/build-data/arch/arm.txt using Plan A...
Hunk #1 succeeded at 5.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_build-data_makefile_unix.in
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_build-data_makefile_unix.in
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_build-data_makefile_unix.in,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/build-data/makefile/unix.in.orig	2016-02-03 07:57:06.000000000 +0000
|+++ src/build-data/makefile/unix.in
--------------------------
Patching file src/build-data/makefile/unix.in using Plan A...
Hunk #1 succeeded at 12.
Hunk #2 succeeded at 89.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_build-data_makefile_unix__shr.in
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_build-data_makefile_unix__shr.in
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_build-data_makefile_unix__shr.in,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/build-data/makefile/unix_shr.in.orig	2016-02-03 07:57:06.000000000 +0000
|+++ src/build-data/makefile/unix_shr.in
--------------------------
Patching file src/build-data/makefile/unix_shr.in using Plan A...
Hunk #1 succeeded at 14.
Hunk #2 succeeded at 103.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_build-data_os_solaris.txt
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_build-data_os_solaris.txt
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_build-data_os_solaris.txt,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|Modern SunOS platforms might not have /usr/ucb. Fixes install on
|SmartOS and other.
|
|--- src/build-data/os/solaris.txt.orig	2016-02-03 07:57:06.000000000 +0000
|+++ src/build-data/os/solaris.txt
--------------------------
Patching file src/build-data/os/solaris.txt using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_entropy_unix_procs_info.txt
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_entropy_unix_procs_info.txt
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_entropy_unix_procs_info.txt,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/entropy/unix_procs/info.txt.orig	2016-02-03 07:57:06.000000000 +0000
|+++ src/entropy/unix_procs/info.txt
--------------------------
Patching file src/entropy/unix_procs/info.txt using Plan A...
Hunk #1 succeeded at 24.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_rec__wri.cpp
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_rec__wri.cpp
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_ssl_rec__wri.cpp,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/ssl/rec_wri.cpp.orig	2016-05-25 20:42:21.289208827 +0000
|+++ src/ssl/rec_wri.cpp
--------------------------
Patching file src/ssl/rec_wri.cpp using Plan A...
Hunk #1 succeeded at 16.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__client.cpp
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__client.cpp
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_ssl_tls__client.cpp,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/ssl/tls_client.cpp.orig	2016-05-25 20:42:19.378772780 +0000
|+++ src/ssl/tls_client.cpp
--------------------------
Patching file src/ssl/tls_client.cpp using Plan A...
Hunk #1 succeeded at 81.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__client.h
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__client.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_ssl_tls__client.h,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/ssl/tls_client.h.orig	2016-05-25 20:42:17.404292837 +0000
|+++ src/ssl/tls_client.h
--------------------------
Patching file src/ssl/tls_client.h using Plan A...
Hunk #1 succeeded at 33.
Hunk #2 succeeded at 51.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__record.h
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__record.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_ssl_tls__record.h,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/ssl/tls_record.h.orig	2016-05-25 20:40:33.153653548 +0000
|+++ src/ssl/tls_record.h
--------------------------
Patching file src/ssl/tls_record.h using Plan A...
Hunk #1 succeeded at 17.
Hunk #2 succeeded at 31.
Hunk #3 succeeded at 58.
Hunk #4 succeeded at 66.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__server.cpp
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__server.cpp
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_ssl_tls__server.cpp,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/ssl/tls_server.cpp.orig	2016-05-25 20:43:18.345421693 +0000
|+++ src/ssl/tls_server.cpp
--------------------------
Patching file src/ssl/tls_server.cpp using Plan A...
Hunk #1 succeeded at 85.
done
=> Verifying /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__server.h
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el9-trunk-x86_64/security/botan1/patches/patch-src_ssl_tls__server.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-src_ssl_tls__server.h,v 1.1 2022/04/01 08:00:34 wiz Exp $
|
|--- src/ssl/tls_server.h.orig	2016-05-25 20:42:12.789110157 +0000
|+++ src/ssl/tls_server.h
--------------------------
Patching file src/ssl/tls_server.h using Plan A...
Hunk #1 succeeded at 36.
Hunk #2 succeeded at 53.
done
===> Creating toolchain wrappers for botan-1.10.17nb2
===> Configuring for botan-1.10.17nb2
   INFO: Guessing to use compiler gcc (use --cc to set)
   INFO: Guessing target OS is linux (use --os to set)
   INFO: Canonicalizized --cpu=amd64 to x86_64/x86_64
   INFO: Target is gcc-linux-x86_64-x86_64
   INFO: Detected gcc version 11
   INFO: Assuming gcc has TR1 (use --with-tr1=none to disable)
   INFO: Skipping, by request only - bzip2 cms cvc gnump openssl zlib
   INFO: Skipping, incompatible CPU - aes_ni aes_ssse3 asm_x86_32 md4_x86_32 md5_x86_32 mp_asm64 mp_x86_32 serpent_x86_32 sha1_x86_32 simd_altivec
   INFO: Skipping, incompatible OS - beos_stats cryptoapi_rng win32_crit_section win32_stats
   INFO: Skipping, incompatible compiler - mp_msvc64 mp_x86_32_msvc
   INFO: Skipping, loaded only if needed by dependency - aes_isa_eng mp_generic simd_scalar
   INFO: Using MP module mp_x86_64
   INFO: Using SIMD module simd_sse2
   INFO: ssl: If you are using TLS in your application definitely consider using the version in 1.11 instead
   INFO: Assuming CPU is little endian
   INFO: Assuming unaligned memory access works
   INFO: Using symlink to link files into build directory
   INFO: Botan 1.10.17 build setup is complete