=> Bootstrap dependency digest>=20211023: found digest-20220214 => Checksum BLAKE2s OK for boost_1_83_0.tar.bz2 => Checksum SHA512 OK for boost_1_83_0.tar.bz2 ===> Installing dependencies for py39-boost-1.83.0 ========================================================================== The following variables will affect the build process of this package, py39-boost-1.83.0. Their current value is shown below: * PKGSRC_BLAS_TYPES = netlib openblas openblas_pthread openblas_openmp * PYTHON_VERSION_DEFAULT = 311 Based on these variables, the following variables have been set: * BLAS_INCLUDES = -I/usr/pkg/include/netlib * BLAS_LIBS = -lblas * BLAS_TYPE = netlib * CBLAS_LIBS = -lcblas -lblas * LAPACKE_LIBS = -llapacke -llapack -lblas * LAPACK_LIBS = -llapack -lblas * PYPACKAGE = python39 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/bin/make clean' after the changes. ========================================================================== => Tool dependency boost-jam-1.83.*: found boost-jam-1.83.0 => Tool dependency mktools-[0-9]*: found mktools-20220614 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Full dependency python39>=3.9.0: found python39-3.9.18 => Full dependency py39-numpy>=1.20.3nb1: found py39-numpy-1.25.2 ===> 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 py39-boost-1.83.0 ===> Extracting for py39-boost-1.83.0 ===> Patching for py39-boost-1.83.0 => Applying pkgsrc patches for py39-boost-1.83.0 => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_archive_basic__archive.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_archive_basic__archive.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_archive_basic__archive.hpp,v 1.4 2021/01/01 08:19:02 ryoon Exp $ | |--- boost/archive/basic_archive.hpp.orig 2020-08-11 14:56:51.000000000 +0000 |+++ boost/archive/basic_archive.hpp -------------------------- Patching file boost/archive/basic_archive.hpp using Plan A... Hunk #1 succeeded at 82. Hunk #2 succeeded at 119. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_asio_detail_config.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_asio_detail_config.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_asio_detail_config.hpp,v 1.7 2021/09/29 16:11:04 adam Exp $ | |--- boost/asio/detail/config.hpp.orig 2021-08-05 09:41:11.000000000 +0000 |+++ boost/asio/detail/config.hpp -------------------------- Patching file boost/asio/detail/config.hpp using Plan A... Hunk #1 succeeded at 1319 (offset 166 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_detail_posix__features.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_detail_posix__features.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_config_detail_posix__features.hpp,v 1.1 2017/08/24 19:31:32 adam Exp $ | |Add OpenBSD conditionals, fix build under OpenBSD 5.5 |OpenBSD has no _POSIX_TIMERS | |--- boost/config/detail/posix_features.hpp.orig 2005-10-14 14:16:26.000000000 +0000 |+++ boost/config/detail/posix_features.hpp -------------------------- Patching file boost/config/detail/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 /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_detail_suffix.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_detail_suffix.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_config_detail_suffix.hpp,v 1.1 2017/08/24 19:31:32 adam Exp $ | |--- boost/config/detail/suffix.hpp.orig 2010-10-01 09:19:44.000000000 +0000 |+++ boost/config/detail/suffix.hpp -------------------------- Patching file boost/config/detail/suffix.hpp using Plan A... Hunk #1 succeeded at 264 (offset 16 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_platform_bsd.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_platform_bsd.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_config_platform_bsd.hpp,v 1.2 2021/09/29 16:11:04 adam Exp $ | |--- boost/config/platform/bsd.hpp.orig 2021-08-05 09:41:19.000000000 +0000 |+++ boost/config/platform/bsd.hpp -------------------------- Patching file boost/config/platform/bsd.hpp using Plan A... Hunk #1 succeeded at 38. Hunk #2 succeeded at 64. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_platform_solaris.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_platform_solaris.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_config_platform_solaris.hpp,v 1.1 2018/01/25 12:33:49 jperkin Exp $ | |Fix threading with clang. | |--- boost/config/platform/solaris.hpp.orig 2018-01-25 11:41:29.424139830 +0000 |+++ boost/config/platform/solaris.hpp -------------------------- Patching file boost/config/platform/solaris.hpp using Plan A... Hunk #1 succeeded at 19. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_stdlib_libcpp.hpp => Applying pkgsrc patch /usr/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 76 (offset 3 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_config_stdlib_libstdcpp3.hpp => Applying pkgsrc patch /usr/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 /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_core_noncopyable.hpp => Applying pkgsrc patch /usr/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.2 2018/12/13 19:22:57 adam Exp $ | |https://svn.boost.org/trac/boost/ticket/6578 | |--- boost/core/noncopyable.hpp.orig 2018-12-05 19:58:16.000000000 +0000 |+++ boost/core/noncopyable.hpp -------------------------- Patching file boost/core/noncopyable.hpp using Plan A... Hunk #1 succeeded at 37. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_core_uncaught__exceptions.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_core_uncaught__exceptions.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_core_uncaught__exceptions.hpp,v 1.1 2019/08/22 21:05:27 tnn Exp $ | |match prototype for __cxa_get_globals() from libc++ | |./boost/core/uncaught_exceptions.hpp:75:30: error: exception specification in declaration does not match previous declaration |/usr/include/c++/cxxabi.h:190:19: note: previous declaration is here |__cxa_eh_globals *__cxa_get_globals(void); | |--- boost/core/uncaught_exceptions.hpp.orig 2019-08-22 20:44:08.783902992 +0000 |+++ boost/core/uncaught_exceptions.hpp -------------------------- Patching file boost/core/uncaught_exceptions.hpp using Plan A... Hunk #1 succeeded at 88 (offset 19 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_math_special__functions_expm1.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_math_special__functions_expm1.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_math_special__functions_expm1.hpp,v 1.1 2017/05/29 14:39:29 ryoon Exp $ | |--- boost/math/special_functions/expm1.hpp.orig 2017-04-17 02:22:22.000000000 +0000 |+++ boost/math/special_functions/expm1.hpp -------------------------- Patching file boost/math/special_functions/expm1.hpp using Plan A... Hunk #1 succeeded at 293 (offset -10 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_math_special__functions_log1p.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_math_special__functions_log1p.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_math_special__functions_log1p.hpp,v 1.1 2017/05/29 14:39:29 ryoon Exp $ | |--- boost/math/special_functions/log1p.hpp.orig 2017-04-17 02:22:22.000000000 +0000 |+++ boost/math/special_functions/log1p.hpp -------------------------- Patching file boost/math/special_functions/log1p.hpp using Plan A... Hunk #1 succeeded at 325 (offset -23 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_math_tools_config.hpp => Applying pkgsrc patch /usr/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.8 2021/09/29 16:11:04 adam Exp $ | |Enable 'long double' support on NetBSD. |NetBSD does not have int128_t, log1pl, etc. | |--- boost/math/tools/config.hpp.orig 2021-08-05 09:42:10.000000000 +0000 |+++ boost/math/tools/config.hpp -------------------------- Patching file boost/math/tools/config.hpp using Plan A... Hunk #1 succeeded at 259 (offset 104 lines). Hunk #2 succeeded at 408 (offset 104 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_math_tools_promotion.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_math_tools_promotion.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_math_tools_promotion.hpp,v 1.3 2023/04/23 14:03:08 adam Exp $ | |Remove the guard; long double should be allowed as a type, even when |long double math functions are not present. Allows py-scipy to build. | |--- boost/math/tools/promotion.hpp.orig 2023-04-21 10:05:48.000000000 +0000 |+++ boost/math/tools/promotion.hpp -------------------------- Patching file boost/math/tools/promotion.hpp using Plan A... Hunk #1 succeeded at 259 (offset 127 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_numeric_ublas_storage.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_numeric_ublas_storage.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_numeric_ublas_storage.hpp,v 1.2 2017/06/28 08:27:00 joerg Exp $ | |--- boost/numeric/ublas/storage.hpp.orig 2017-06-27 09:07:20.588660202 +0000 |+++ boost/numeric/ublas/storage.hpp -------------------------- Patching file boost/numeric/ublas/storage.hpp using Plan A... Hunk #1 succeeded at 27 (offset 1 line). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_process_detail_posix_handles.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_process_detail_posix_handles.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_process_detail_posix_handles.hpp,v 1.2 2020/09/10 07:54:52 tnn Exp $ | |dirfd(3) on NetBSD is implemented as a macro and cannot use namespace prefix. | |--- boost/process/detail/posix/handles.hpp.orig 2020-04-22 13:35:49.000000000 +0000 |+++ boost/process/detail/posix/handles.hpp -------------------------- Patching file boost/process/detail/posix/handles.hpp using Plan A... Hunk #1 succeeded at 33 (offset 2 lines). Hunk #2 succeeded at 121 (offset 2 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_process_detail_posix_is__running.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_process_detail_posix_is__running.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_process_detail_posix_is__running.hpp,v 1.1 2020/09/09 06:38:52 tnn Exp $ | |Cannot use static asserts on WIFEXITED() & friends because the |internal _W_INT macro uses (void*) which is not allowed in constexprs. | |--- boost/process/detail/posix/is_running.hpp.orig 2020-04-22 13:35:49.000000000 +0000 |+++ boost/process/detail/posix/is_running.hpp -------------------------- Patching file boost/process/detail/posix/is_running.hpp using Plan A... Hunk #1 succeeded at 17. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_property__tree_detail_xml__parser__read__rapidxml.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_property__tree_detail_xml__parser__read__rapidxml.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_property__tree_detail_xml__parser__read__rapidxml.hpp,v 1.1 2017/08/24 19:31:32 adam Exp $ | |--- boost/property_tree/detail/xml_parser_read_rapidxml.hpp.orig 2017-08-19 16:49:45.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. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_stacktrace_detail_collect__unwind.ipp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_stacktrace_detail_collect__unwind.ipp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_stacktrace_detail_collect__unwind.ipp,v 1.2 2019/07/01 04:00:10 ryoon Exp $ | |Fix build with gcc 5.4.0 "error: expected id-expression before numeric constant" | |--- boost/stacktrace/detail/collect_unwind.ipp.orig 2019-04-09 19:36:33.000000000 +0000 |+++ boost/stacktrace/detail/collect_unwind.ipp -------------------------- Patching file boost/stacktrace/detail/collect_unwind.ipp using Plan A... Hunk #1 succeeded at 48. Hunk #2 succeeded at 57. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_test_impl_execution__monitor.ipp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_test_impl_execution__monitor.ipp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_test_impl_execution__monitor.ipp,v 1.4 2020/01/12 10:10:04 adam Exp $ | |--- boost/test/impl/execution_monitor.ipp.orig 2019-12-10 00:20:00.000000000 +0000 |+++ boost/test/impl/execution_monitor.ipp -------------------------- Patching file boost/test/impl/execution_monitor.ipp using Plan A... Hunk #1 succeeded at 171. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_thread_pthread_thread__data.hpp => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boost_thread_pthread_thread__data.hpp Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boost_thread_pthread_thread__data.hpp,v 1.2 2020/05/06 13:33:53 adam Exp $ | |--- boost/thread/pthread/thread_data.hpp.orig 2020-04-22 13:36:07.000000000 +0000 |+++ boost/thread/pthread/thread_data.hpp -------------------------- Patching file boost/thread/pthread/thread_data.hpp using Plan A... Hunk #1 succeeded at 32. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boostcpp.jam => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-boostcpp.jam Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-boostcpp.jam,v 1.4 2019/07/01 04:00:10 ryoon Exp $ | |Find pkgsrc libraries. |Allow exclusion of all libraries. | |--- boostcpp.jam.orig 2019-04-09 19:35:15.000000000 +0000 |+++ boostcpp.jam -------------------------- Patching file boostcpp.jam using Plan A... Hunk #1 succeeded at 549 (offset 29 lines). done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_config_configure => Applying pkgsrc patch /usr/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 /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_config_test_boost__no__range__based__for.ipp => Applying pkgsrc patch /usr/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 /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_context_src_asm_jump_arm_aapcs_elf_gas.S => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_context_src_asm_jump_arm_aapcs_elf_gas.S Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-libs_context_src_asm_jump_arm_aapcs_elf_gas.S,v 1.3 2018/12/13 19:22:57 adam Exp $ | |Work-around for NetBSD earmv6hf toolchain failing to assemble |v(ld|st)mia instruction if it's not explicitly told there's an FPU. | |--- libs/context/src/asm/jump_arm_aapcs_elf_gas.S.orig 2018-12-05 19:58:16.000000000 +0000 |+++ libs/context/src/asm/jump_arm_aapcs_elf_gas.S -------------------------- Patching file libs/context/src/asm/jump_arm_aapcs_elf_gas.S using Plan A... Hunk #1 succeeded at 40. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_context_src_asm_ontop_arm_aapcs_elf_gas.S => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_context_src_asm_ontop_arm_aapcs_elf_gas.S Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-libs_context_src_asm_ontop_arm_aapcs_elf_gas.S,v 1.3 2018/12/13 19:22:57 adam Exp $ | |Work-around for NetBSD earmv6hf toolchain failing to assemble |v(ld|st)mia instruction if it's not explicitly told there's an FPU. | |--- libs/context/src/asm/ontop_arm_aapcs_elf_gas.S.orig 2018-12-05 19:58:16.000000000 +0000 |+++ libs/context/src/asm/ontop_arm_aapcs_elf_gas.S -------------------------- Patching file libs/context/src/asm/ontop_arm_aapcs_elf_gas.S using Plan A... Hunk #1 succeeded at 40. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-libs_fiber_build_Jamfile.v2 => Applying pkgsrc patch /usr/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.2 2021/01/01 08:19:02 ryoon Exp $ | |Build with -fvisibility=hidden on SunOS. | |--- libs/fiber/build/Jamfile.v2.orig 2020-08-11 14:55:48.000000000 +0000 |+++ libs/fiber/build/Jamfile.v2 -------------------------- Patching file libs/fiber/build/Jamfile.v2 using Plan A... Hunk #1 succeeded at 24. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-tools_build_src_engine_build.sh => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-tools_build_src_engine_build.sh Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_build_src_engine_build.sh,v 1.4 2021/09/29 16:11:04 adam Exp $ | |Fix for bad substitution. | |--- tools/build/src/engine/build.sh.orig 2021-08-05 09:43:08.000000000 +0000 |+++ tools/build/src/engine/build.sh -------------------------- Patching file tools/build/src/engine/build.sh using Plan A... Hunk #1 succeeded at 23. done => Verifying /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-tools_build_src_tools_gcc.jam => Applying pkgsrc patch /usr/pkgsrc/devel/py-boost/../../meta-pkgs/boost/patches/patch-tools_build_src_tools_gcc.jam Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tools_build_src_tools_gcc.jam,v 1.5 2018/05/11 14:45:23 jperkin Exp $ | |SunOS supports soname. | |--- tools/build/src/tools/gcc.jam.orig 2018-04-11 13:49:09.000000000 +0000 |+++ tools/build/src/tools/gcc.jam -------------------------- Patching file tools/build/src/tools/gcc.jam using Plan A... Hunk #1 succeeded at 980 (offset 58 lines). done ===> Creating toolchain wrappers for py39-boost-1.83.0 ===> Configuring for py39-boost-1.83.0 => Fixing install_name for Darwin. /usr/bin/find /usr/pkgsrc/devel/py-boost/work/boost_1_83_0 -type f -exec /usr/bin/touch {} + => Checking for portability problems in extracted files echo 'using python : 3.9 :' '/usr/pkg/bin/python3.9 : /usr/pkg/include/python3.9 ;' >/usr/pkgsrc/devel/py-boost/work/boost_1_83_0/user-config.jam