=> Bootstrap dependency digest>=20010302: found digest-20160304 ===> Skipping vulnerability checks. WARNING: No /var/db/pkg/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'. => Checksum SHA1 OK for boost-1.63.0v3/boost_1_63_0.tar.bz2 => Checksum RMD160 OK for boost-1.63.0v3/boost_1_63_0.tar.bz2 => Checksum SHA512 OK for boost-1.63.0v3/boost_1_63_0.tar.bz2 ===> Installing dependencies for py34-boost-1.63.0nb1 ========================================================================== The following variables will affect the build process of this package, py34-boost-1.63.0nb1. Their current value is shown below: * PYTHON_VERSION_DEFAULT = 27 Based on these variables, the following variables have been set: * PYPACKAGE = python34 You may want to abort the process now with CTRL-C and change their value before continuing. Be sure to run `/usr/bin/make clean' after the changes. ========================================================================== => Tool dependency checkperms>=1.1: found checkperms-1.11nb1 => Build dependency boost-headers-1.63.*: found boost-headers-1.63.0 => Build dependency boost-jam-1.63.*: found boost-jam-1.63.0 => Build dependency cwrappers>=20150314: found cwrappers-20170112 => Full dependency python34>=3.4: found python34-3.4.6 => Full dependency py34-numpy>=1.0: found py34-numpy-1.12.1nb2 ===> Overriding tools for py34-boost-1.63.0nb1 ===> Extracting for py34-boost-1.63.0nb1 ===> Patching for py34-boost-1.63.0nb1 => Applying pkgsrc patches for py34-boost-1.63.0nb1 => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-aa => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-aa Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aa,v 1.10 2012/08/27 08:49:09 adam Exp $ | |--- boostcpp.jam.orig 2012-07-27 18:15:55.000000000 +0000 |+++ boostcpp.jam -------------------------- Patching file boostcpp.jam using Plan A... Hunk #1 succeeded at 303 (offset 54 lines). Hunk #2 succeeded at 511 (offset 1 line). done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ab => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ab Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ab,v 1.6 2014/05/13 18:48:49 ryoon Exp $ | |--- boost/config/platform/bsd.hpp.orig 2011-03-07 13:07:30.000000000 +0000 |+++ boost/config/platform/bsd.hpp -------------------------- Patching file boost/config/platform/bsd.hpp using Plan A... Hunk #1 succeeded at 37. Hunk #2 succeeded at 56. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ac => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ac Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ac,v 1.8 2013/02/12 21:07:22 adam Exp $ | |--- boost/config/suffix.hpp.orig 2010-10-01 09:19:44.000000000 +0000 |+++ boost/config/suffix.hpp -------------------------- Patching file boost/config/suffix.hpp using Plan A... Hunk #1 succeeded at 248. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ad => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ad Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ad,v 1.12 2012/08/27 08:49:09 adam Exp $ | |--- boost/archive/basic_archive.hpp.orig 2012-08-27 07:38:03.000000000 +0000 |+++ boost/archive/basic_archive.hpp -------------------------- Patching file boost/archive/basic_archive.hpp using Plan A... Hunk #1 succeeded at 115. Hunk #2 succeeded at 151. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ae => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ae Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ae,v 1.8 2014/08/13 10:56:36 adam Exp $ | |Pass CFLAGS to the compiler. | |--- tools/build/src/engine/build.sh.orig 2011-02-24 08:42:55.000000000 +0000 |+++ tools/build/src/engine/build.sh -------------------------- Patching file tools/build/src/engine/build.sh using Plan A... Hunk #1 succeeded at 274 (offset 37 lines). done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ag => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ag Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ag,v 1.8 2014/08/13 10:56:36 adam Exp $ | |Pass CFLAGS to the compiler. | |--- tools/build/src/engine/build.jam.orig 2011-02-24 08:50:34.000000000 +0000 |+++ tools/build/src/engine/build.jam -------------------------- Patching file tools/build/src/engine/build.jam using Plan A... Hunk #1 succeeded at 199 (offset 7 lines). done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-aq => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-aq Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aq,v 1.9 2016/10/07 17:51:11 adam Exp $ | |--- boost/test/impl/execution_monitor.ipp.orig 2016-10-05 08:52:21.000000000 +0000 |+++ boost/test/impl/execution_monitor.ipp -------------------------- Patching file boost/test/impl/execution_monitor.ipp using Plan A... Hunk #1 succeeded at 163 (offset -3 lines). Hunk #2 succeeded at 363 (offset -3 lines). Hunk #3 succeeded at 378 (offset -3 lines). Hunk #4 succeeded at 608 (offset -3 lines). done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ar => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-ar Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ar,v 1.3 2012/07/02 07:02:26 adam Exp $ | |--- boost/property_tree/detail/xml_parser_read_rapidxml.hpp.orig 2010-10-15 12:40:04.000000000 +0000 |+++ boost/property_tree/detail/xml_parser_read_rapidxml.hpp -------------------------- Patching file boost/property_tree/detail/xml_parser_read_rapidxml.hpp using Plan A... Hunk #1 succeeded at 103 (offset -3 lines). done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_atomic_detail_ops_gcc_sparc.hpp => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_atomic_detail_ops_gcc_sparc.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_atomic_detail_ops_gcc_sparc.hpp,v 1.2 2017/01/01 15:32:47 adam Exp $ | |provide a fence_before_store() for sparc, which fixes the build. | |--- boost/atomic/detail/ops_gcc_sparc.hpp.orig 2017-01-01 02:18:57.000000000 +0000 |+++ boost/atomic/detail/ops_gcc_sparc.hpp -------------------------- Patching file boost/atomic/detail/ops_gcc_sparc.hpp using Plan A... Hunk #1 succeeded at 36. Hunk #2 succeeded at 63. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_posix__features.hpp => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_posix__features.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_config_posix__features.hpp,v 1.1 2014/05/13 18:48:49 ryoon Exp $ | |* Add OpenBSD conditionals, fix build under OpenBSD 5.5 |* OpenBSD has no _POSIX_TIMERS | |--- boost/config/posix_features.hpp.orig 2005-10-14 14:16:26.000000000 +0000 |+++ boost/config/posix_features.hpp -------------------------- Patching file boost/config/posix_features.hpp using Plan A... Hunk #1 succeeded at 18. Hunk #2 succeeded at 33. Hunk #3 succeeded at 49. Hunk #4 succeeded at 58. Hunk #5 succeeded at 76. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_stdlib_libcpp.hpp => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_stdlib_libcpp.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_config_stdlib_libcpp.hpp,v 1.5 2017/01/01 15:32:47 adam Exp $ | |--- boost/config/stdlib/libcpp.hpp.orig 2017-01-01 02:18:57.000000000 +0000 |+++ boost/config/stdlib/libcpp.hpp -------------------------- Patching file boost/config/stdlib/libcpp.hpp using Plan A... Hunk #1 succeeded at 73. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_stdlib_libstdcpp3.hpp => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_stdlib_libstdcpp3.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_config_stdlib_libstdcpp3.hpp,v 1.2 2015/04/17 14:04:47 adam Exp $ | |* Fix build under NetBSD with GCC 4.8.3 in base. | GCC 4.8.3 does not define _GLIBCXX_HAVE_GTHR_DEFAULT | in /usr/include/g++/bits/c++config.h. | |--- boost/config/stdlib/libstdcpp3.hpp.orig 2015-03-24 18:27:48.000000000 +0000 |+++ boost/config/stdlib/libstdcpp3.hpp -------------------------- Patching file boost/config/stdlib/libstdcpp3.hpp using Plan A... Hunk #1 succeeded at 37. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_core_noncopyable.hpp => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_core_noncopyable.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_core_noncopyable.hpp,v 1.1 2014/08/13 10:56:36 adam Exp $ | |https://svn.boost.org/trac/boost/ticket/6578 | |--- boost/core/noncopyable.hpp.orig 2014-07-15 09:08:59.000000000 +0000 |+++ boost/core/noncopyable.hpp -------------------------- Patching file boost/core/noncopyable.hpp using Plan A... Hunk #1 succeeded at 22. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_math_tools_config.hpp => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_math_tools_config.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_math_tools_config.hpp,v 1.3 2016/02/12 14:24:01 ryoon Exp $ | |* NetBSD has no int128_t | |--- boost/math/tools/config.hpp.orig 2015-12-11 18:00:52.000000000 +0000 |+++ boost/math/tools/config.hpp -------------------------- Patching file boost/math/tools/config.hpp using Plan A... Hunk #1 succeeded at 267 (offset -12 lines). done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_regex_config.hpp => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_regex_config.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_regex_config.hpp,v 1.1 2014/05/13 18:48:49 ryoon Exp $ | |* Fix OpenBSD build | |--- boost/regex/config.hpp.orig 2012-07-16 08:38:23.000000000 +0000 |+++ boost/regex/config.hpp -------------------------- Patching file boost/regex/config.hpp using Plan A... Hunk #1 succeeded at 84 (offset 9 lines). done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_config_configure => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_config_configure Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-libs_config_configure,v 1.1 2013/04/12 13:34:42 joerg Exp $ | |--- libs/config/configure.orig 2013-03-30 16:16:50.000000000 +0000 |+++ libs/config/configure -------------------------- Patching file libs/config/configure using Plan A... Hunk #1 succeeded at 3050. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_config_test_boost__no__range__based__for.ipp => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_config_test_boost__no__range__based__for.ipp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-libs_config_test_boost__no__range__based__for.ipp,v 1.1 2015/09/24 23:02:54 tnn Exp $ | |This configure test goes into an infinite loop with GCC 5.2.0 at |optimization level -O2 when -std=c++11 is not selected. |-O0 makes it segfault instead which is more appropriate as it counts |as a test failure, but is still horribly broken. |The expected result for trying to compile with c++11 features when |c++11 is not enabled should arguably be a compile error. | |--- libs/config/test/boost_no_range_based_for.ipp.orig 2015-08-04 11:44:49.000000000 +0000 |+++ libs/config/test/boost_no_range_based_for.ipp -------------------------- Patching file libs/config/test/boost_no_range_based_for.ipp using Plan A... Hunk #1 succeeded at 9. done => Verifying /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_fiber_build_Jamfile.v2 => Applying pkgsrc patch /data/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_fiber_build_Jamfile.v2 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-libs_fiber_build_Jamfile.v2,v 1.1 2017/03/09 16:30:12 jperkin Exp $ | |Build with -fvisibility=hidden on SunOS. | |--- libs/fiber/build/Jamfile.v2.orig 2017-03-09 15:52:54.326169384 +0000 |+++ libs/fiber/build/Jamfile.v2 -------------------------- Patching file libs/fiber/build/Jamfile.v2 using Plan A... Hunk #1 succeeded at 18. done ===> Creating toolchain wrappers for py34-boost-1.63.0nb1 ===> Configuring for py34-boost-1.63.0nb1 => Fixing prefix. => Fixing install_name for Darwin. cd /data/scratch/devel/py-boost/work/boost_1_63_0 && /usr/bin/find . -type f -print | /usr/bin/xargs /usr/bin/touch => Checking for portability problems in extracted files /bin/cp -f /usr/pkg/include/boost/config/user.hpp /data/scratch/devel/py-boost/work/boost_1_63_0/boost/config/user.hpp echo 'using python : 3.4 :' '/usr/pkg/bin/python3.4 ;' >/data/scratch/devel/py-boost/work/boost_1_63_0/user-config.jam