>>> Building on macppc-2 under mail/gmail-oauth2
	DIST = [mail/gmail-oauth2:gmail-oauth2-0.20190529-e3229155.tar.gz]
	FULLPKGNAME = gmail-oauth2-0.20190529p5
	RDEPENDS = [lang/python/3]
(Junk lock obtained for macppc-2 at 1746501371.67)
Still tainted: host marked nojunk by cad/coil64
>>> Running junk in mail/gmail-oauth2 at 1746501372.14
Can't run junk because of lock on cad/coil64
(Junk lock released for macppc-2 at 1746501382.77)
distfiles size=22713
>>> Running build in mail/gmail-oauth2 at 1746501382.95
===> mail/gmail-oauth2
===> Building from scratch gmail-oauth2-0.20190529p5
===>  Checking files for gmail-oauth2-0.20190529p5
`/usr/ports/distfiles/gmail-oauth2-0.20190529-e3229155.tar.gz' is up to date.
>> (SHA256) all files: OK
===>  Extracting for gmail-oauth2-0.20190529p5
===>  Patching for gmail-oauth2-0.20190529p5
===>   Applying OpenBSD patch patch-python_oauth2_py
Hmm...  I can't seem to find a patch in there anywhere.
***>   patch-python_oauth2_py did not apply cleanly
===>   Failed patches: 
    patch-python_oauth2_py

*** Error 1 in mail/gmail-oauth2 (/usr/ports/infrastructure/mk/bsd.port.mk:2939 '/usr/obj/ports/gmail-oauth2-0.20190529/.patch_done': @if cd...)
*** Error 2 in mail/gmail-oauth2 (/usr/ports/infrastructure/mk/bsd.port.mk:2712 'build': @lock=gmail-oauth2-0.20190529p5;  export _LOCKS_HEL...)
===> Exiting mail/gmail-oauth2 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 1746501385.65
max_stuck=0.00/junk=10.90/build=2.87
Error: job failed with 512 on macppc-2 at 1746501385