=> Bootstrap dependency digest>=20211023: found digest-20211023 WARNING: [license.mk] Every package should define a LICENSE. => Checksum BLAKE2s OK for blitz-0.8.tar.gz => Checksum SHA512 OK for blitz-0.8.tar.gz ===> Installing dependencies for blitz++-0.8nb3 => Tool dependency libtool-base>=2.4.2nb9: found libtool-base-2.4.6nb3 => Tool dependency gmake>=3.81: found gmake-4.3nb2 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Build dependency libtool-fortran>=2.4.2nb9: found libtool-fortran-2.4.6nb2 => Build dependency cwrappers>=20150314: found cwrappers-20180325 => Full dependency gcc7>=7.0: found gcc7-7.5.0nb5 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Overriding tools for blitz++-0.8nb3 ===> Extracting for blitz++-0.8nb3 ===> Patching for blitz++-0.8nb3 => Applying pkgsrc patches for blitz++-0.8nb3 => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-aa => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-aa Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aa,v 1.2 2005/09/05 14:06:59 adam Exp $ | |--- Makefile.in.orig 2005-09-05 15:36:03.000000000 +0000 |+++ Makefile.in -------------------------- Patching file Makefile.in using Plan A... Hunk #1 succeeded at 283. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-ab => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-ab Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ab,v 1.3 2006/02/02 14:10:45 joerg Exp $ | |--- blitz/funcs.h.orig 2006-02-02 14:05:27.000000000 +0000 |+++ blitz/funcs.h -------------------------- Patching file blitz/funcs.h using Plan A... Hunk #1 succeeded at 583. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-ac => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-ac Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ac,v 1.3 2006/02/02 14:10:45 joerg Exp $ | |--- blitz/mathfunc.h.orig 2006-02-02 14:06:44.000000000 +0000 |+++ blitz/mathfunc.h -------------------------- Patching file blitz/mathfunc.h using Plan A... Hunk #1 succeeded at 1545. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-ad => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-ad Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ad,v 1.3 2008/06/20 01:10:02 joerg Exp $ | |--- doc/doxygen/Makefile.in.orig 2008-06-19 15:41:31.000000000 +0000 |+++ doc/doxygen/Makefile.in -------------------------- Patching file doc/doxygen/Makefile.in using Plan A... Hunk #1 succeeded at 474. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-blitz_compiler.h => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/math/blitz++/patches/patch-blitz_compiler.h Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-blitz_compiler.h,v 1.1 2011/12/29 16:33:09 joerg Exp $ | |--- blitz/compiler.h.orig 2011-12-29 14:24:12.000000000 +0000 |+++ blitz/compiler.h -------------------------- Patching file blitz/compiler.h using Plan A... Hunk #1 succeeded at 114. done ===> Creating toolchain wrappers for blitz++-0.8nb3 ===> Configuring for blitz++-0.8nb3 => 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 build system type... x86_64--netbsd checking host system type... x86_64--netbsd checking target system type... x86_64--netbsd checking for a BSD-compatible install... /usr/bin/install -c -o pbulk -g wheel checking whether build environment is sane... yes checking for gawk... /usr/bin/awk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no configure: Configuring blitz 0.8 for x86_64--netbsd checking for x86_64--netbsd-xlf... gfortran checking for Fortran 77 compiler default output file name... a.out checking whether the Fortran 77 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 Fortran 77 compiler... yes checking whether gfortran accepts -g... yes checking for x86_64--netbsd-xlf90... gfortran checking whether we are using the GNU Fortran compiler... yes checking whether gfortran accepts -g... yes checking for Fortran flag needed to allow free-form source... -ffree-form checking for Fortran flag to compile .f90 files... none checking whether using gfortran and gfortran preset flags... yes configure: Blitz++ has not been tuned for this platform. You may have trouble building fortran benchmarks, and performance may be unexciting. checking for x86_64--netbsd-xlc++... c++ checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of c++... gcc3 checking whether using c++ preset flags... yes configure: No flags preset found for c++ checking compiler specific header... gnu/bzconfig.h checking whether to enable C++/Fortran 64-bit compilation flags... no checking for x86_64--netbsd-gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /usr/pkg/bin/gsed checking for egrep... grep -E checking for ld used by gcc... /tmp/math/blitz++/work/.cwrapper/bin/ld checking if the linker (/tmp/math/blitz++/work/.cwrapper/bin/ld) is GNU ld... yes checking for /tmp/math/blitz++/work/.cwrapper/bin/ld option to reload object files... -r checking for BSD-compatible nm... nm checking whether ln -s works... yes checking how to recognise dependent libraries... match_pattern /lib[^/]+(\.so|_pic\.a)$ checking how to run the C preprocessor... gcc -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... c++ -E checking the maximum length of command line arguments... (cached) 262144 checking command to parse nm output from gcc object... ok checking for objdir... .libs checking for x86_64--netbsd-ar... no checking for ar... ar checking for x86_64--netbsd-ranlib... no checking for ranlib... ranlib checking for x86_64--netbsd-strip... no checking for strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/tmp/math/blitz++/work/.cwrapper/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... NetBSD ld.elf_so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes 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 c++... /tmp/math/blitz++/work/.cwrapper/bin/ld checking if the linker (/tmp/math/blitz++/work/.cwrapper/bin/ld) is GNU ld... yes checking whether the c++ linker (/tmp/math/blitz++/work/.cwrapper/bin/ld) supports shared libraries... yes checking for c++ option to produce PIC... -fPIC checking if c++ PIC flag -fPIC works... yes checking if c++ supports -c -o file.o... yes checking whether the c++ linker (/tmp/math/blitz++/work/.cwrapper/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... NetBSD ld.elf_so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... no checking whether to build static libraries... yes checking for gfortran option to produce PIC... -fPIC checking if gfortran PIC flag -fPIC works... yes checking if gfortran supports -c -o file.o... yes checking whether the gfortran linker (/tmp/math/blitz++/work/.cwrapper/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... NetBSD ld.elf_so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking for sin in -lm... yes configure: Checking to see if there is a usable BLAS library kicking around... (If so, Blitz++ will use BLAS library to run benchmarks against if you build the benchmarks. Blitz++ itself does NOT use BLAS). checking for daxpy_ in -lblas... no checking for daxpy in -lblas... no checking for DAXPY in -lblas... no checking for daxpy__ in -lblas... no checking whether to enable c++ optimization flags... no checking whether to enable c++ debug flags... no configure: C++ compiler (c++ -O2 -fPIC -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include ) characteristics configure: Checking major C++ language features checking whether the compiler implements namespaces... yes checking whether the compiler supports exceptions... yes checking whether the compiler supports Run-Time Type Identification... yes checking whether the compiler supports member constants... yes checking whether the compiler accepts the old for scoping rules... no configure: Now for some of the new keywords checking whether the compiler supports the explicit keyword... yes checking whether the compiler supports the mutable keyword... yes checking whether the compiler recognizes typename... yes checking whether the compiler supports the Numerical C Extensions Group restrict keyword... no checking whether the compiler recognizes the '__restrict__' keyword... yes checking whether the compiler recognizes bool as a built-in type... yes configure: Does your compiler understand the newfangled casting syntax? checking whether the compiler supports const_cast<>... yes checking whether the compiler supports static_cast<>... yes checking whether the compiler supports reinterpret_cast<>... yes checking whether the compiler supports dynamic_cast<>... yes configure: Okay, now the important stuff -- templates checking whether the compiler supports basic templates... yes checking whether the compiler supports partial specialization... yes checking whether the compiler supports partial ordering... yes checking whether the compiler supports default template parameters... yes checking whether the compiler supports member templates... yes checking whether the compiler supports member templates outside the class declaration... yes checking whether the compiler recognizes the full specialization syntax... yes checking whether the compiler supports function templates with non-type parameters... yes checking whether the compiler supports template-qualified base class specifiers... no checking whether the compiler supports template-qualified return types... yes checking whether the compiler supports explicit template function qualification... yes checking whether the compiler supports templates as template arguments... yes checking whether the compiler supports use of the template keyword as a qualifier... yes checking whether the compiler supports function matching with argument types which are template scope-qualified... yes checking whether the compiler will support the vector type promotion mechanism... yes checking whether the compiler supports numeric traits promotions... yes checking whether the compiler handle computations inside an enum... yes checking whether the compiler handles (int) casts in enum computations... yes configure: Which library features does your compiler provide? checking whether the compiler has complex... yes checking whether the compiler has standard complex functions... yes checking whether the compiler has numeric_limits... yes checking whether the compiler has header... yes checking whether the compiler has valarray... yes checking whether the compiler has complex math functions... yes checking whether the compiler has more complex math functions... no checking whether the compiler supports IEEE math library... no checking whether the compiler supports System V math library... no checking whether the compiler has C math functions in namespace std... yes checking whether complex math functions are in namespace std... yes checking whether the compiler supports ISO C++ standard library... yes checking whether the compiler supports Standard Template Library... yes checking whether the compiler has getrusage() function... yes configure: CXX = c++ CXXFLAGS = -O2 -fPIC -D_FORTIFY_SOURCE=2 -I/usr/pkg/include -I/usr/include CXX_OPTIMIZE_FLAGS = CXX_DEBUG_FLAGS = CXXFFLAGS = F77 = gfortran FFLAGS = -O F77_OPTIMIZE_FLAGS = FC = gfortran FCFLAGS = -g -O2 -ffree-form FC_OPTIMIZE_FLAGS = FORTLIBS = BLASLIB = checking our pkgconfig libname... blitz checking our pkgconfig version... 0.8 checking our pkgconfig_libdir... ${libdir}/pkgconfig expanded our pkgconfig_libdir... /usr/pkg/lib/pkgconfig checking our pkgconfig_libfile... blitz.pc checking our pkgconfig description... blitz Library checking our pkgconfig requires... checking our pkgconfig ext libs... -lblitz -lm checking our pkgconfig cppflags... -I/usr/pkg/include -I/usr/include noninstalled pkgconfig -L /tmp/math/blitz++/work/blitz-0.8/src/.libs noninstalled pkgconfig -I /tmp/math/blitz++/work/blitz-0.8/. configure: creating ./config.status config.status: creating Makefile config.status: creating bin/Makefile config.status: creating blitz/Makefile config.status: creating blitz/array/Makefile config.status: creating blitz/generate/Makefile config.status: creating blitz/meta/Makefile config.status: creating random/Makefile config.status: creating lib/Makefile config.status: creating testsuite/Makefile config.status: creating examples/Makefile config.status: creating benchmarks/Makefile config.status: creating benchmarks/plot_benchmarks.m config.status: creating doc/Makefile config.status: creating doc/examples/Makefile config.status: creating doc/stencils/Makefile config.status: creating doc/doxygen/Makefile config.status: creating doc/doxygen/Doxyfile config.status: creating blitz/config.h config.status: executing depfiles commands config.status: executing blitz.pc commands config.status: creating blitz.pc.in config.status: creating blitz.pc config.status: creating blitz-uninstalled.pc configure: The configure script has generated makefiles for your platform. You have several options now: make lib Check the compiler and create libblitz.a make check-testsuite Build and check the testsuite make check-examples Build and check the examples make check-benchmarks Build and check the benchmarks (takes a long time) make install Install Blitz++ => Modifying libtool scripts to use pkgsrc libtool => Modifying libtool scripts to use pkgsrc depcomp