=> Bootstrap dependency digest>=20010302: found digest-20160304 => Checksum SHA1 OK for veriwell-2.8.7.tar.gz => Checksum RMD160 OK for veriwell-2.8.7.tar.gz => Checksum SHA512 OK for veriwell-2.8.7.tar.gz ===> Installing dependencies for veriwell-2.8.7 => Build dependency cwrappers>=20150314: found cwrappers-20180325 ===> Overriding tools for veriwell-2.8.7 ===> Extracting for veriwell-2.8.7 ===> Patching for veriwell-2.8.7 ===> Creating toolchain wrappers for veriwell-2.8.7 ===> Configuring for veriwell-2.8.7 => 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... /usr/bin/install -c -o pbulk -g users checking whether build environment is sane... yes checking for a thread-safe mkdir -p... config/install-sh -c -d checking for gawk... /usr/bin/awk checking whether make sets $(MAKE)... yes checking use 32 bit compile... no checking enable lxt support... yes checking enable lxt2 support... yes checking for C++ compiler default output file name... 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 clang++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of clang++... gcc3 checking for x86_64-unknown-freebsd11-gcc... clang checking whether we are using the GNU C compiler... yes checking whether clang accepts -g... yes checking for clang option to accept ISO C89... none needed checking dependency style of clang... gcc3 checking for a BSD-compatible install... /usr/bin/install -c -o pbulk -g users checking for x86_64-unknown-freebsd11-ranlib... no checking for ranlib... ranlib checking for help2man... no *** Warning: No suitable help2man found. *** The help2man package is essential for rebuilding veriwell man pages. You can get away without it when simply building from snapshots or major releases. checking build system type... x86_64-unknown-freebsd11 checking host system type... x86_64-unknown-freebsd11 checking for a sed that does not truncate output... /var/pkgsrc/work/cad/veriwell/work/.tools/bin/sed checking for grep that handles long lines and -e... (cached) /usr/bin/grep checking for egrep... (cached) /usr/bin/egrep checking for ld used by clang... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... clang -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 dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... clang++ -E checking for x86_64-unknown-freebsd11-g77... f77 checking whether we are using the GNU Fortran 77 compiler... no checking whether f77 accepts -g... no checking the maximum length of command line arguments... 196608 checking command to parse /usr/bin/nm output from clang object... ok checking for objdir... .libs checking for x86_64-unknown-freebsd11-ar... no checking for ar... ar checking for x86_64-unknown-freebsd11-ranlib... ranlib checking for x86_64-unknown-freebsd11-strip... no checking for strip... strip checking if clang supports -fno-rtti -fno-exceptions... yes checking for clang option to produce PIC... -fPIC checking if clang PIC flag -fPIC works... yes checking if clang static flag -static works... yes checking if clang supports -c -o file.o... yes checking whether the clang linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... no checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking if libtool supports shared libraries... no checking whether to build shared libraries... no checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by clang++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the clang++ linker (/usr/bin/ld) supports shared libraries... no checking for clang++ option to produce PIC... -fPIC checking if clang++ PIC flag -fPIC works... yes checking if clang++ static flag -static works... yes checking if clang++ supports -c -o file.o... yes checking whether the clang++ linker (/usr/bin/ld) supports shared libraries... no checking dynamic linker characteristics... no checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... no checking whether to build shared libraries... no checking whether to build static libraries... yes checking for f77 option to produce PIC... -fPIC checking if f77 PIC flag -fPIC works... no checking if f77 static flag -static works... no checking if f77 supports -c -o file.o... no checking whether the f77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... PKGSRC-WARNING: Something is trying to run the fortran compiler, PKGSRC-WARNING: but it is not added to USE_LANGUAGES in the package Makefile. no checking how to hardcode library paths into programs... immediate checking for gperf... no *** Warning: No suitable gperf found. *** The gperf package is essential for building veriwell from CVS sources, or modifying the parse engine of veriwell itself. You can get away without it when simply building from snapshots or major releases. checking for bison... no *** Warning: No suitable bison found. *** The bison package is essential for building veriwell from CVS sources, or modifying the parse engine of veriwell itself. You can get away without it when simply building from snapshots or major releases. checking for gzwrite in -lz... yes checking for BZ2_bzwrite in -lbz2... yes checking for a readline compatible library... -ledit checking readline/readline.h usability... no checking readline/readline.h presence... no checking for readline/readline.h... no checking readline.h usability... no checking readline.h presence... no checking for readline.h... no checking whether readline supports history... yes checking history.h usability... no checking history.h presence... no checking for history.h... no checking readline/history.h usability... no checking readline/history.h presence... no checking for readline/history.h... no checking for ANSI C header files... (cached) yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking for memory.h... (cached) yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdlib.h... (cached) yes checking stdarg.h usability... yes checking stdarg.h presence... yes checking for stdarg.h... yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking whether byte ordering is bigendian... no checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking return type of signal handlers... void checking for vprintf... yes checking for _doprnt... no checking for memmove... yes checking for memset... yes checking for pow... no checking for strchr... yes checking for strdup... yes checking for strrchr... yes checking for vfscanf in stdio.h... yes configure: creating ./config.status config.status: creating Makefile config.status: creating replace/Makefile config.status: creating replace/libz/Makefile config.status: creating replace/libbz2/Makefile config.status: creating src/Makefile config.status: creating lxt/Makefile config.status: creating doc/Makefile config.status: creating config.h config.status: executing depfiles commands WARNING: *** Please consider adding fortran to USE_LANGUAGES in the package Makefile.