+ case "${usergroup_phase}" in + local run_cmd + run_cmd=run_su + shift + run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/libowfat-0.34nb1/work.log + su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/libowfat-0.34nb1/work.log => Checksum BLAKE2s OK for libowfat-0.34.tar.xz => Checksum SHA512 OK for libowfat-0.34.tar.xz ===> Installing dependencies for libowfat-0.34nb1 => Tool dependency gmake>=3.81: found gmake-4.4.1 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 ===> Overriding tools for libowfat-0.34nb1 ===> Extracting for libowfat-0.34nb1 cd /home/pbulk/build/devel/libowfat/work/libowfat-0.34; /usr/bin/mv tai/tai_now.3 tai/tai_now_libowfat.3; /usr/bin/mv tai/tai_pack.3 tai/tai_pack_libowfat.3; /usr/bin/mv taia/taia_now.3 taia/taia_now_libowfat.3; /usr/bin/mv taia/taia_pack.3 taia/taia_pack_libowfat.3 ===> Patching for libowfat-0.34nb1 => Applying pkgsrc patches for libowfat-0.34nb1 => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-GNUmakefile => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-GNUmakefile Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-GNUmakefile,v 1.1 2022/01/23 13:30:33 schmonz Exp $ | |Follow hier(7) and support PKGMANDIR. | |--- GNUmakefile.orig 2018-08-24 12:00:46.000000000 +0000 |+++ GNUmakefile -------------------------- Patching file GNUmakefile using Plan A... Hunk #1 succeeded at 4. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-io_io__sendfile.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-io_io__sendfile.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-io_io__sendfile.c,v 1.2 2023/11/09 19:26:00 schmonz Exp $ | |Fix Illumos build. | |--- io/io_sendfile.c.orig 2022-04-25 14:21:38.000000000 +0000 |+++ io/io_sendfile.c -------------------------- Patching file io/io_sendfile.c using Plan A... Hunk #1 succeeded at 44 (offset 1 line). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-io_io__waituntil2.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-io_io__waituntil2.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-io_io__waituntil2.c,v 1.1 2024/12/08 23:08:15 hgutch Exp $ | |- EVFILT_READ/EVFILT_WRITE are magic numbers, not bit flags. Without | this, the EVFILT_READ test always fails on NetBSD (and always | succeeds on FreeBSD/OpenBSD) and as a result, calling io_wait() | always immediately returns (instead of blocking) even if there is no | data to be read. In practice this means that programs using this | will most likely spin at 100% CPU. |- Fix test for EVFILT_READ instead of EVFILT_WRITE. |- Fix the test for the whole "e->canread" optimization; this did not | lead to wrong behavior, but this invalidates the whole optimization | of libowfat not asking the kernel for additional data to read until | the consumer has finally read from this descriptor. | |--- io/io_waituntil2.c.orig 2022-03-11 12:07:54.000000000 +0000 |+++ io/io_waituntil2.c -------------------------- Patching file io/io_waituntil2.c using Plan A... Hunk #1 succeeded at 184. Hunk #2 succeeded at 294. Hunk #3 succeeded at 308. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-mmap_mmap__readat.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-mmap_mmap__readat.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-mmap_mmap__readat.c,v 1.2 2023/11/09 19:26:00 schmonz Exp $ | |Fix Illumos build. | |--- mmap/mmap_readat.c.orig 2019-04-23 13:25:27.000000000 +0000 |+++ mmap/mmap_readat.c -------------------------- Patching file mmap/mmap_readat.c using Plan A... Hunk #1 succeeded at 3. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-scan_scan__httpdate.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-scan_scan__httpdate.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-scan_scan__httpdate.c,v 1.1 2022/11/03 00:00:08 schmonz Exp $ | |Fix macOS build with the 13.0 SDK, which has its own definition of |__deprecated__. | |--- scan/scan_httpdate.c.orig 2016-04-27 14:07:50 |+++ scan/scan_httpdate.c -------------------------- Patching file scan/scan_httpdate.c using Plan A... Hunk #1 succeeded at 6 (offset 2 lines). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-scan_scan__iso8601.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-scan_scan__iso8601.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-scan_scan__iso8601.c,v 1.2 2022/11/03 00:00:08 schmonz Exp $ | |Fix Illumos build. Then fix macOS build with the 13.0 SDK, which has its |own definition of __deprecated__. | |--- scan/scan_iso8601.c.orig 2016-04-27 14:07:50 |+++ scan/scan_iso8601.c -------------------------- Patching file scan/scan_iso8601.c using Plan A... Hunk #1 succeeded at 6 (offset 2 lines). Hunk #2 succeeded at 49 (offset 2 lines). done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-socket_socket__accept4__flags.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-socket_socket__accept4__flags.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-socket_socket__accept4__flags.c,v 1.1 2023/11/09 19:26:00 schmonz Exp $ | |Don't use socket flags when they're not available. | |--- socket/socket_accept4_flags.c.orig 2021-04-27 17:39:43.000000000 +0000 |+++ socket/socket_accept4_flags.c -------------------------- Patching file socket/socket_accept4_flags.c using Plan A... Hunk #1 succeeded at 84. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-socket_socket__accept6__flags.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-socket_socket__accept6__flags.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-socket_socket__accept6__flags.c,v 1.1 2023/11/09 19:26:00 schmonz Exp $ | |Don't use socket flags when they're not available. | |--- socket/socket_accept6_flags.c.orig 2021-04-27 17:39:44.000000000 +0000 |+++ socket/socket_accept6_flags.c -------------------------- Patching file socket/socket_accept6_flags.c using Plan A... Hunk #1 succeeded at 98. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-socket_socket__quickack.c => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-socket_socket__quickack.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-socket_socket__quickack.c,v 1.2 2023/11/09 19:26:00 schmonz Exp $ | |Follow socket/socket_fastopen.c's example to fix Illumos build. | |--- socket/socket_quickack.c.orig 2019-02-21 12:39:44.000000000 +0000 |+++ socket/socket_quickack.c -------------------------- Patching file socket/socket_quickack.c using Plan A... Hunk #1 succeeded at 6. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-tai_tai__now__libowfat.3 => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-tai_tai__now__libowfat.3 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tai_tai__now__libowfat.3,v 1.1 2019/07/16 21:39:11 schmonz Exp $ | |Avoid conflict with libtai's manpages. | |--- tai/tai_now_libowfat.3.orig 2017-05-13 22:51:52.000000000 +0000 |+++ tai/tai_now_libowfat.3 -------------------------- Patching file tai/tai_now_libowfat.3 using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 15. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-tai_tai__pack__libowfat.3 => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-tai_tai__pack__libowfat.3 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-tai_tai__pack__libowfat.3,v 1.1 2019/07/16 21:39:11 schmonz Exp $ | |Avoid conflict with libtai's manpages. | |--- tai/tai_pack_libowfat.3.orig 2017-05-13 22:51:52.000000000 +0000 |+++ tai/tai_pack_libowfat.3 -------------------------- Patching file tai/tai_pack_libowfat.3 using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 11. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-taia_taia__now__libowfat.3 => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-taia_taia__now__libowfat.3 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-taia_taia__now__libowfat.3,v 1.1 2019/07/16 21:39:11 schmonz Exp $ | |Avoid conflict with libtai's manpages. | |--- taia/taia_now_libowfat.3.orig 2017-05-13 22:51:53.000000000 +0000 |+++ taia/taia_now_libowfat.3 -------------------------- Patching file taia/taia_now_libowfat.3 using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 19. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-taia_taia__pack__libowfat.3 => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/devel/libowfat/patches/patch-taia_taia__pack__libowfat.3 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-taia_taia__pack__libowfat.3,v 1.1 2019/07/16 21:39:11 schmonz Exp $ | |Avoid conflict with libtai's manpages. | |--- taia/taia_pack_libowfat.3.orig 2017-05-13 22:51:53.000000000 +0000 |+++ taia/taia_pack_libowfat.3 -------------------------- Patching file taia/taia_pack_libowfat.3 using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 11. done ===> Creating toolchain wrappers for libowfat-0.34nb1 ===> Configuring for libowfat-0.34nb1 => Checking for portability problems in extracted files