+ 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/gappa-1.3.5/work.log + su pbulk -c '"$@"' make /usr/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/gappa-1.3.5/work.log => Bootstrap dependency digest>=20211023: found digest-20220214 => Checksum BLAKE2s OK for gappa-1.3.5.tar.gz => Checksum SHA512 OK for gappa-1.3.5.tar.gz ===> Installing dependencies for gappa-1.3.5 => 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 => Build dependency boost-headers-1.78.*: found boost-headers-1.78.0 => Full dependency gmp>=5.0.1: found gmp-6.2.1nb3 => Full dependency mpfr>=4.0.0: found mpfr-4.1.1nb1 ===> Overriding tools for gappa-1.3.5 ===> Extracting for gappa-1.3.5 ===> Patching for gappa-1.3.5 => Applying pkgsrc patches for gappa-1.3.5 => Verifying /data/jenkins/workspace/pkgsrc-el7-trunk-x86_64/math/gappa/patches/patch-Remakefile.in => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-el7-trunk-x86_64/math/gappa/patches/patch-Remakefile.in Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-Remakefile.in,v 1.2 2020/07/17 17:30:13 riastradh Exp $ | |Install to DESTDIR. | |https://gitlab.inria.fr/gappa/gappa/-/commit/ba4dbb3ef66bbdd9d1f3d660a293515df0b57b43 | |--- Remakefile.in.orig 2019-05-24 12:52:39.000000000 +0000 |+++ Remakefile.in -------------------------- Patching file Remakefile.in using Plan A... Hunk #1 succeeded at 136. done ===> Creating toolchain wrappers for gappa-1.3.5 ===> Configuring for gappa-1.3.5 => 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 whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking for x86_64-redhat-linux-gcc... cc checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking for flex... no checking for lex... no checking for bison... no checking for byacc... no checking how to run the C preprocessor... cc -E checking for gcc... gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... (cached) none needed checking how to run the C preprocessor... gcc -E checking how to run the C++ preprocessor... c++ -E checking for g++... g++ checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... yes checking how to run the C++ preprocessor... g++ -E checking for __gmpz_init in -lgmp... yes checking for mpfr_snprintf in -lmpfr... yes checking for Boost (>=1.32)... yes checking for tr1/unordered_map... yes configure: building remake... /tmp/ccnNEbJo.o: In function `main': remake.cpp:(.text.startup+0x772): warning: the use of `tempnam' is dangerous, better use `mkstemp' configure: creating ./config.status config.status: creating stamp-config_h config.status: creating Remakefile config.status: creating config.h