>>> Building on macppc-2 under mail/rcube-dkimstatus
	DIST = [mail/rcube-dkimstatus:dkimstatus-0.9.5.tar.gz]
	FULLPKGNAME = rcube-dkimstatus-0.9.5p7
	RDEPENDS = [mail/roundcubemail]
(Junk lock obtained for macppc-2 at 1746511667.71)
Still tainted: host marked nojunk by cad/coil64
>>> Running junk in mail/rcube-dkimstatus at 1746511669.91
Can't run junk because of lock on cad/coil64
(Junk lock released for macppc-2 at 1746511684.69)
distfiles size=12020
>>> Running build in mail/rcube-dkimstatus at 1746511684.90
===> mail/rcube-dkimstatus
===> Building from scratch rcube-dkimstatus-0.9.5p7
===>  Checking files for rcube-dkimstatus-0.9.5p7
`/usr/ports/distfiles/dkimstatus-0.9.5.tar.gz' is up to date.
>> (SHA256) all files: OK
===>  Extracting for rcube-dkimstatus-0.9.5p7
===>  Patching for rcube-dkimstatus-0.9.5p7
===>   Applying OpenBSD patch patch-dkimstatus_php
Hmm...  I can't seem to find a patch in there anywhere.
***>   patch-dkimstatus_php did not apply cleanly
===>   Failed patches: 
    patch-dkimstatus_php

*** Error 1 in mail/rcube-dkimstatus (/usr/ports/infrastructure/mk/bsd.port.mk:2939 '/usr/obj/ports/rcube-dkimstatus-0.9.5/.patch_done': @if...)
*** Error 2 in mail/rcube-dkimstatus (/usr/ports/infrastructure/mk/bsd.port.mk:2712 'build': @lock=rcube-dkimstatus-0.9.5p7;  export _LOCKS_...)
===> Exiting mail/rcube-dkimstatus with an error
*** Error 1 in /usr/ports (infrastructure/mk/bsd.port.subdir.mk:144 'build': @: ${echo_msg:=echo};  : ${target:=build};  for i in ; do  eval...)
>>> Ended at 1746511687.21
max_stuck=0.00/junk=15.08/build=2.49
Error: job failed with 512 on macppc-2 at 1746511687