>>> Building on macppc-2 under shells/sash
	DIST = [shells/sash:sash-3.8.tar.gz]
	FULLPKGNAME = sash-3.8p1
(Junk lock failure for macppc-2 at 1746532806.92887)
Received IO
(Junk lock obtained for macppc-2 at 1746532825.98)
Woken up shells/sash
Woken up shells/sash
Still tainted: host marked nojunk by cad/coil64
>>> Running junk in shells/sash at 1746532842.57
Can't run junk because of lock on cad/coil64
(Junk lock released for macppc-2 at 1746532860.80)
Woken up devel/p5-Data-ShowTable
distfiles size=53049
>>> Running build in shells/sash at 1746532862.49
===> shells/sash
===> Building from scratch sash-3.8p1
===>  Checking files for sash-3.8p1
`/usr/ports/distfiles/sash-3.8.tar.gz' is up to date.
>> (SHA256) all files: OK
===>  Extracting for sash-3.8p1
===>  Patching for sash-3.8p1
===>   Applying OpenBSD patch patch-cmd_ls_c
Hmm...  I can't seem to find a patch in there anywhere.
***>   patch-cmd_ls_c did not apply cleanly
===>   Applying OpenBSD patch patch-cmds_c
Hmm...  I can't seem to find a patch in there anywhere.
***>   patch-cmds_c did not apply cleanly
===>   Failed patches: 
    patch-cmd_ls_c
    patch-cmds_c

*** Error 1 in shells/sash (/usr/ports/infrastructure/mk/bsd.port.mk:2939 '/usr/obj/ports/sash-3.8/.patch_done': @if cd /usr/ports/shells/sa...)
*** Error 2 in shells/sash (/usr/ports/infrastructure/mk/bsd.port.mk:2712 'build': @lock=sash-3.8p1;  export _LOCKS_HELD=" sash-3.8p1";   /u...)
===> Exiting shells/sash 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 1746532864.55
max_stuck=16.91/waiting-for-lock #948=31.38/junk=18.40/build=3.34
Error: job failed with 512 on macppc-2 at 1746532864