=> Bootstrap dependency digest>=20010302: found digest-20190127
===> Skipping vulnerability checks.
WARNING: No /var/db/pkg/pkg-vulnerabilities file found.
WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'.
=> Checksum SHA1 OK for sdk-source-20191111.tar.xz
=> Checksum RMD160 OK for sdk-source-20191111.tar.xz
=> Checksum SHA512 OK for sdk-source-20191111.tar.xz
===> Installing dependencies for ppc-morphos-gcc-9-9.2.0nb1
=> Tool dependency autoconf>=2.50: found autoconf-2.69nb9
=> Tool dependency gmake>=3.81: found gmake-4.2.1nb1
=> Tool dependency gsed>=3.0.2: found gsed-4.8
=> Tool dependency gtar-base>=1.13.25: found gtar-base-1.32nb1
=> Tool dependency perl>=5.0: found perl-5.30.2
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency ppc-morphos-binutils-[0-9]*: found ppc-morphos-binutils-2.33.1
=> Full dependency ppc-morphos-sdk-[0-9]*: found ppc-morphos-sdk-20191111nb2
=> Full dependency gmp>=5.0.1: found gmp-6.2.0
=> Full dependency mpfr>=4.0.0: found mpfr-4.0.2nb1
=> Full dependency mpcomplex>=1.0.3nb1: found mpcomplex-1.1.0
===> Overriding tools for ppc-morphos-gcc-9-9.2.0nb1
===> Extracting for ppc-morphos-gcc-9-9.2.0nb1
===> Patching for ppc-morphos-gcc-9-9.2.0nb1
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/config/gthr.m4 gcc-9.2.0.new/config/gthr.m4
|--- gcc-9.2.0.old/config/gthr.m4	2012-10-15 16:10:30.000000000 +0300
|+++ gcc-9.2.0.new/config/gthr.m4	2019-08-15 14:56:14.381573378 +0300
--------------------------
Patching file config/gthr.m4 using Plan A...
Hunk #1 succeeded at 21.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/config.rpath gcc-9.2.0.new/config.rpath
|--- gcc-9.2.0.old/config.rpath	2011-02-13 13:45:53.000000000 +0200
|+++ gcc-9.2.0.new/config.rpath	2019-08-15 14:56:14.381573378 +0300
--------------------------
Patching file config.rpath using Plan A...
Hunk #1 succeeded at 159.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/configure gcc-9.2.0.new/configure
|--- gcc-9.2.0.old/configure	2019-04-14 12:52:22.000000000 +0300
|+++ gcc-9.2.0.new/configure	2019-08-15 14:56:14.385573436 +0300
--------------------------
Patching file configure using Plan A...
Hunk #1 succeeded at 3864.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/configure.ac gcc-9.2.0.new/configure.ac
|--- gcc-9.2.0.old/configure.ac	2019-04-14 12:52:22.000000000 +0300
|+++ gcc-9.2.0.new/configure.ac	2019-08-15 14:56:14.385573436 +0300
--------------------------
Patching file configure.ac using Plan A...
Hunk #1 succeeded at 1146.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/fixincludes/configure.ac gcc-9.2.0.new/fixincludes/configure.ac
|--- gcc-9.2.0.old/fixincludes/configure.ac	2018-10-31 19:03:16.000000000 +0200
|+++ gcc-9.2.0.new/fixincludes/configure.ac	2019-08-15 14:56:14.385573436 +0300
--------------------------
Patching file fixincludes/configure.ac using Plan A...
Hunk #1 succeeded at 53.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/fixincludes/fixlib.h gcc-9.2.0.new/fixincludes/fixlib.h
|--- gcc-9.2.0.old/fixincludes/fixlib.h	2016-09-30 19:36:18.000000000 +0300
|+++ gcc-9.2.0.new/fixincludes/fixlib.h	2019-08-15 14:56:14.385573436 +0300
--------------------------
Patching file fixincludes/fixlib.h using Plan A...
Hunk #1 succeeded at 32.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/fixincludes/Makefile.in gcc-9.2.0.new/fixincludes/Makefile.in
|--- gcc-9.2.0.old/fixincludes/Makefile.in	2017-01-17 11:38:48.000000000 +0200
|+++ gcc-9.2.0.new/fixincludes/Makefile.in	2019-08-15 14:56:14.385573436 +0300
--------------------------
Patching file fixincludes/Makefile.in using Plan A...
Hunk #1 succeeded at 52.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/common/config/rs6000/rs6000-common.c gcc-9.2.0.new/gcc/common/config/rs6000/rs6000-common.c
|--- gcc-9.2.0.old/gcc/common/config/rs6000/rs6000-common.c	2019-03-11 15:58:44.000000000 +0200
|+++ gcc-9.2.0.new/gcc/common/config/rs6000/rs6000-common.c	2019-08-15 14:56:14.385573436 +0300
--------------------------
Patching file gcc/common/config/rs6000/rs6000-common.c using Plan A...
Hunk #1 succeeded at 28.
Hunk #2 succeeded at 232.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config/rs6000/morphos.c gcc-9.2.0.new/gcc/config/rs6000/morphos.c
|--- gcc-9.2.0.old/gcc/config/rs6000/morphos.c	1970-01-01 02:00:00.000000000 +0200
|+++ gcc-9.2.0.new/gcc/config/rs6000/morphos.c	2019-08-15 14:56:14.385573436 +0300
--------------------------
(Creating file gcc/config/rs6000/morphos.c...)
Patching file gcc/config/rs6000/morphos.c using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config/rs6000/morphos.h gcc-9.2.0.new/gcc/config/rs6000/morphos.h
|--- gcc-9.2.0.old/gcc/config/rs6000/morphos.h	1970-01-01 02:00:00.000000000 +0200
|+++ gcc-9.2.0.new/gcc/config/rs6000/morphos.h	2019-08-15 14:56:14.385573436 +0300
--------------------------
(Creating file gcc/config/rs6000/morphos.h...)
Patching file gcc/config/rs6000/morphos.h using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config/rs6000/morphos.opt gcc-9.2.0.new/gcc/config/rs6000/morphos.opt
|--- gcc-9.2.0.old/gcc/config/rs6000/morphos.opt	1970-01-01 02:00:00.000000000 +0200
|+++ gcc-9.2.0.new/gcc/config/rs6000/morphos.opt	2019-08-15 14:56:14.385573436 +0300
--------------------------
(Creating file gcc/config/rs6000/morphos.opt...)
Patching file gcc/config/rs6000/morphos.opt using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config/rs6000/morphos-protos.h gcc-9.2.0.new/gcc/config/rs6000/morphos-protos.h
|--- gcc-9.2.0.old/gcc/config/rs6000/morphos-protos.h	1970-01-01 02:00:00.000000000 +0200
|+++ gcc-9.2.0.new/gcc/config/rs6000/morphos-protos.h	2019-08-15 14:56:14.385573436 +0300
--------------------------
(Creating file gcc/config/rs6000/morphos-protos.h...)
Patching file gcc/config/rs6000/morphos-protos.h using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config/rs6000/morphos-stdint.h gcc-9.2.0.new/gcc/config/rs6000/morphos-stdint.h
|--- gcc-9.2.0.old/gcc/config/rs6000/morphos-stdint.h	1970-01-01 02:00:00.000000000 +0200
|+++ gcc-9.2.0.new/gcc/config/rs6000/morphos-stdint.h	2019-08-15 14:56:14.385573436 +0300
--------------------------
(Creating file gcc/config/rs6000/morphos-stdint.h...)
Patching file gcc/config/rs6000/morphos-stdint.h using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config/rs6000/rs6000.c gcc-9.2.0.new/gcc/config/rs6000/rs6000.c
|--- gcc-9.2.0.old/gcc/config/rs6000/rs6000.c	2019-08-04 22:23:59.000000000 +0300
|+++ gcc-9.2.0.new/gcc/config/rs6000/rs6000.c	2019-08-15 14:56:14.389573493 +0300
--------------------------
Patching file gcc/config/rs6000/rs6000.c using Plan A...
Hunk #1 succeeded at 107.
Hunk #2 succeeded at 144.
Hunk #3 succeeded at 1621.
Hunk #4 succeeded at 5807.
Hunk #5 succeeded at 7503.
Hunk #6 succeeded at 8239.
Hunk #7 succeeded at 8718.
Hunk #8 succeeded at 8936.
Hunk #9 succeeded at 10093.
Hunk #10 succeeded at 10353.
Hunk #11 succeeded at 21107.
Hunk #12 succeeded at 21369.
Hunk #13 succeeded at 21428.
Hunk #14 succeeded at 21537.
Hunk #15 succeeded at 21576.
Hunk #16 succeeded at 24818.
Hunk #17 succeeded at 24933.
Hunk #18 succeeded at 24972.
Hunk #19 succeeded at 25086.
Hunk #20 succeeded at 25123.
Hunk #21 succeeded at 25154.
Hunk #22 succeeded at 25221.
Hunk #23 succeeded at 27382.
Hunk #24 succeeded at 27988.
Hunk #25 succeeded at 28062.
Hunk #26 succeeded at 28941.
Hunk #27 succeeded at 33262.
Hunk #28 succeeded at 33292.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config/rs6000/rs6000.md gcc-9.2.0.new/gcc/config/rs6000/rs6000.md
|--- gcc-9.2.0.old/gcc/config/rs6000/rs6000.md	2019-04-21 11:25:44.000000000 +0300
|+++ gcc-9.2.0.new/gcc/config/rs6000/rs6000.md	2019-08-15 14:56:14.393573552 +0300
--------------------------
Patching file gcc/config/rs6000/rs6000.md using Plan A...
Hunk #1 succeeded at 10127.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config/rs6000/t-morphos gcc-9.2.0.new/gcc/config/rs6000/t-morphos
|--- gcc-9.2.0.old/gcc/config/rs6000/t-morphos	1970-01-01 02:00:00.000000000 +0200
|+++ gcc-9.2.0.new/gcc/config/rs6000/t-morphos	2019-08-15 14:56:14.393573552 +0300
--------------------------
(Creating file gcc/config/rs6000/t-morphos...)
Patching file gcc/config/rs6000/t-morphos using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config.gcc gcc-9.2.0.new/gcc/config.gcc
|--- gcc-9.2.0.old/gcc/config.gcc	2019-08-03 23:16:22.000000000 +0300
|+++ gcc-9.2.0.new/gcc/config.gcc	2019-08-15 14:56:14.393573552 +0300
--------------------------
Patching file gcc/config.gcc using Plan A...
Hunk #1 succeeded at 2668.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/config.host gcc-9.2.0.new/gcc/config.host
|--- gcc-9.2.0.old/gcc/config.host	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/gcc/config.host	2019-08-15 14:56:14.393573552 +0300
--------------------------
Patching file gcc/config.host using Plan A...
Hunk #1 succeeded at 263.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/configure gcc-9.2.0.new/gcc/configure
|--- gcc-9.2.0.old/gcc/configure	2019-06-26 12:15:46.000000000 +0300
|+++ gcc-9.2.0.new/gcc/configure	2019-08-15 14:56:14.397573610 +0300
--------------------------
Patching file gcc/configure using Plan A...
Hunk #1 succeeded at 9949.
Hunk #2 succeeded at 9973.
Hunk #3 succeeded at 10030.
Hunk #4 succeeded at 10141.
Hunk #5 succeeded at 11861.
Hunk #6 succeeded at 12206.
Hunk #7 succeeded at 13205.
Hunk #8 succeeded at 22025.
Hunk #9 succeeded at 22183.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/configure.ac gcc-9.2.0.new/gcc/configure.ac
|--- gcc-9.2.0.old/gcc/configure.ac	2019-06-26 12:15:46.000000000 +0300
|+++ gcc-9.2.0.new/gcc/configure.ac	2019-08-15 14:56:14.397573610 +0300
--------------------------
Patching file gcc/configure.ac using Plan A...
Hunk #1 succeeded at 1300.
Hunk #2 succeeded at 1651.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/coretypes.h gcc-9.2.0.new/gcc/coretypes.h
|--- gcc-9.2.0.old/gcc/coretypes.h	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/gcc/coretypes.h	2019-08-15 14:56:14.397573610 +0300
--------------------------
Patching file gcc/coretypes.h using Plan A...
Hunk #1 succeeded at 325.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/cppdefault.c gcc-9.2.0.new/gcc/cppdefault.c
|--- gcc-9.2.0.old/gcc/cppdefault.c	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/gcc/cppdefault.c	2019-08-15 14:56:14.397573610 +0300
--------------------------
Patching file gcc/cppdefault.c using Plan A...
Hunk #1 succeeded at 40.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/gcov-io.h gcc-9.2.0.new/gcc/gcov-io.h
|--- gcc-9.2.0.old/gcc/gcov-io.h	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/gcc/gcov-io.h	2019-08-15 14:56:14.397573610 +0300
--------------------------
Patching file gcc/gcov-io.h using Plan A...
Hunk #1 succeeded at 179.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/ginclude/stddef.h gcc-9.2.0.new/gcc/ginclude/stddef.h
|--- gcc-9.2.0.old/gcc/ginclude/stddef.h	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/gcc/ginclude/stddef.h	2019-08-15 14:56:14.429574075 +0300
--------------------------
Patching file gcc/ginclude/stddef.h using Plan A...
Hunk #1 succeeded at 1.
Hunk #2 succeeded at 46.
Hunk #3 succeeded at 87.
Hunk #4 succeeded at 200.
Hunk #5 succeeded at 359.
Hunk #6 succeeded at 391.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/gcc/Makefile.in gcc-9.2.0.new/gcc/Makefile.in
|--- gcc-9.2.0.old/gcc/Makefile.in	2019-04-25 17:32:16.000000000 +0300
|+++ gcc-9.2.0.new/gcc/Makefile.in	2019-08-15 14:56:14.397573610 +0300
--------------------------
Patching file gcc/Makefile.in using Plan A...
Hunk #1 succeeded at 617.
Hunk #2 succeeded at 1033.
Hunk #3 succeeded at 2160.
Hunk #4 succeeded at 2876.
Hunk #5 succeeded at 3460.
Hunk #6 succeeded at 3898.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libada/Makefile.in gcc-9.2.0.new/libada/Makefile.in
|--- gcc-9.2.0.old/libada/Makefile.in	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libada/Makefile.in	2019-08-15 14:56:14.401573667 +0300
--------------------------
Patching file libada/Makefile.in using Plan A...
Hunk #1 succeeded at 68.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libcpp/files.c gcc-9.2.0.new/libcpp/files.c
|--- gcc-9.2.0.old/libcpp/files.c	2019-04-03 20:56:41.000000000 +0300
|+++ gcc-9.2.0.new/libcpp/files.c	2019-08-15 14:56:14.401573667 +0300
--------------------------
Patching file libcpp/files.c using Plan A...
Hunk #1 succeeded at 39.
Hunk #2 succeeded at 234.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libffi/configure gcc-9.2.0.new/libffi/configure
|--- gcc-9.2.0.old/libffi/configure	2018-10-31 19:03:16.000000000 +0200
|+++ gcc-9.2.0.new/libffi/configure	2019-08-15 14:56:14.401573667 +0300
--------------------------
Patching file libffi/configure using Plan A...
Hunk #1 succeeded at 5837.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libffi/include/Makefile.in gcc-9.2.0.new/libffi/include/Makefile.in
|--- gcc-9.2.0.old/libffi/include/Makefile.in	2018-10-31 19:03:16.000000000 +0200
|+++ gcc-9.2.0.new/libffi/include/Makefile.in	2019-08-15 14:56:14.401573667 +0300
--------------------------
Patching file libffi/include/Makefile.in using Plan A...
Hunk #1 succeeded at 321.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgcc/config/rs6000/gthr-morphos.c gcc-9.2.0.new/libgcc/config/rs6000/gthr-morphos.c
|--- gcc-9.2.0.old/libgcc/config/rs6000/gthr-morphos.c	1970-01-01 02:00:00.000000000 +0200
|+++ gcc-9.2.0.new/libgcc/config/rs6000/gthr-morphos.c	2019-08-15 14:56:14.401573667 +0300
--------------------------
(Creating file libgcc/config/rs6000/gthr-morphos.c...)
Patching file libgcc/config/rs6000/gthr-morphos.c using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgcc/config/rs6000/gthr-morphos.h gcc-9.2.0.new/libgcc/config/rs6000/gthr-morphos.h
|--- gcc-9.2.0.old/libgcc/config/rs6000/gthr-morphos.h	1970-01-01 02:00:00.000000000 +0200
|+++ gcc-9.2.0.new/libgcc/config/rs6000/gthr-morphos.h	2019-08-15 14:56:14.401573667 +0300
--------------------------
(Creating file libgcc/config/rs6000/gthr-morphos.h...)
Patching file libgcc/config/rs6000/gthr-morphos.h using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgcc/config/rs6000/t-gthr-morphos gcc-9.2.0.new/libgcc/config/rs6000/t-gthr-morphos
|--- gcc-9.2.0.old/libgcc/config/rs6000/t-gthr-morphos	1970-01-01 02:00:00.000000000 +0200
|+++ gcc-9.2.0.new/libgcc/config/rs6000/t-gthr-morphos	2019-08-15 14:56:14.401573667 +0300
--------------------------
(Creating file libgcc/config/rs6000/t-gthr-morphos...)
Patching file libgcc/config/rs6000/t-gthr-morphos using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgcc/config.host gcc-9.2.0.new/libgcc/config.host
|--- gcc-9.2.0.old/libgcc/config.host	2019-01-17 14:29:13.000000000 +0200
|+++ gcc-9.2.0.new/libgcc/config.host	2019-08-15 14:56:14.401573667 +0300
--------------------------
Patching file libgcc/config.host using Plan A...
Hunk #1 succeeded at 1089.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgcc/configure gcc-9.2.0.new/libgcc/configure
|--- gcc-9.2.0.old/libgcc/configure	2018-10-31 19:03:16.000000000 +0200
|+++ gcc-9.2.0.new/libgcc/configure	2019-08-15 14:56:14.401573667 +0300
--------------------------
Patching file libgcc/configure using Plan A...
Hunk #1 succeeded at 5550.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgcc/crtstuff.c gcc-9.2.0.new/libgcc/crtstuff.c
|--- gcc-9.2.0.old/libgcc/crtstuff.c	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libgcc/crtstuff.c	2019-08-15 14:56:14.401573667 +0300
--------------------------
Patching file libgcc/crtstuff.c using Plan A...
Hunk #1 succeeded at 155.
Hunk #2 succeeded at 388.
Hunk #3 succeeded at 426.
Hunk #4 succeeded at 671.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgcc/Makefile.in gcc-9.2.0.new/libgcc/Makefile.in
|--- gcc-9.2.0.old/libgcc/Makefile.in	2019-01-18 13:32:53.000000000 +0200
|+++ gcc-9.2.0.new/libgcc/Makefile.in	2019-08-15 14:56:14.401573667 +0300
--------------------------
Patching file libgcc/Makefile.in using Plan A...
Hunk #1 succeeded at 199.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgfortran/configure gcc-9.2.0.new/libgfortran/configure
|--- gcc-9.2.0.old/libgfortran/configure	2019-08-12 10:40:32.000000000 +0300
|+++ gcc-9.2.0.new/libgfortran/configure	2019-08-15 14:56:14.405573726 +0300
--------------------------
Patching file libgfortran/configure using Plan A...
Hunk #1 succeeded at 7223.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgfortran/Makefile.in gcc-9.2.0.new/libgfortran/Makefile.in
|--- gcc-9.2.0.old/libgfortran/Makefile.in	2019-08-12 10:40:32.000000000 +0300
|+++ gcc-9.2.0.new/libgfortran/Makefile.in	2019-08-15 14:56:14.405573726 +0300
--------------------------
Patching file libgfortran/Makefile.in using Plan A...
Hunk #1 succeeded at 735.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgomp/configure gcc-9.2.0.new/libgomp/configure
|--- gcc-9.2.0.old/libgomp/configure	2019-08-12 10:40:32.000000000 +0300
|+++ gcc-9.2.0.new/libgomp/configure	2019-08-15 14:56:14.409573784 +0300
--------------------------
Patching file libgomp/configure using Plan A...
Hunk #1 succeeded at 5679.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libgomp/Makefile.in gcc-9.2.0.new/libgomp/Makefile.in
|--- gcc-9.2.0.old/libgomp/Makefile.in	2019-08-12 10:40:32.000000000 +0300
|+++ gcc-9.2.0.new/libgomp/Makefile.in	2019-08-15 14:56:14.409573784 +0300
--------------------------
Patching file libgomp/Makefile.in using Plan A...
Hunk #1 succeeded at 521.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libiberty/configure gcc-9.2.0.new/libiberty/configure
|--- gcc-9.2.0.old/libiberty/configure	2018-10-31 19:03:16.000000000 +0200
|+++ gcc-9.2.0.new/libiberty/configure	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libiberty/configure using Plan A...
Hunk #1 succeeded at 6631.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libiberty/stack-limit.c gcc-9.2.0.new/libiberty/stack-limit.c
|--- gcc-9.2.0.old/libiberty/stack-limit.c	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libiberty/stack-limit.c	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libiberty/stack-limit.c using Plan A...
Hunk #1 succeeded at 39.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libobjc/configure gcc-9.2.0.new/libobjc/configure
|--- gcc-9.2.0.old/libobjc/configure	2019-08-12 10:40:31.000000000 +0300
|+++ gcc-9.2.0.new/libobjc/configure	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libobjc/configure using Plan A...
Hunk #1 succeeded at 2509.
Hunk #2 succeeded at 4960.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libobjc/Makefile.in gcc-9.2.0.new/libobjc/Makefile.in
|--- gcc-9.2.0.old/libobjc/Makefile.in	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libobjc/Makefile.in	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libobjc/Makefile.in using Plan A...
Hunk #1 succeeded at 48.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libobjc/objc/objc.h gcc-9.2.0.new/libobjc/objc/objc.h
|--- gcc-9.2.0.old/libobjc/objc/objc.h	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libobjc/objc/objc.h	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libobjc/objc/objc.h using Plan A...
Hunk #1 succeeded at 51.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libobjc/objc-sync.c gcc-9.2.0.new/libobjc/objc-sync.c
|--- gcc-9.2.0.old/libobjc/objc-sync.c	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libobjc/objc-sync.c	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libobjc/objc-sync.c using Plan A...
Hunk #1 succeeded at 174.
Hunk #2 succeeded at 194.
Hunk #3 succeeded at 460.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libobjc/objects.c gcc-9.2.0.new/libobjc/objects.c
|--- gcc-9.2.0.old/libobjc/objects.c	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libobjc/objects.c	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libobjc/objects.c using Plan A...
Hunk #1 succeeded at 36.
Hunk #2 succeeded at 94.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libobjc/thr.c gcc-9.2.0.new/libobjc/thr.c
|--- gcc-9.2.0.old/libobjc/thr.c	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libobjc/thr.c	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libobjc/thr.c using Plan A...
Hunk #1 succeeded at 35.
Hunk #2 succeeded at 83.
Hunk #3 succeeded at 177.
Hunk #4 succeeded at 208.
Hunk #5 succeeded at 221.
Hunk #6 succeeded at 265.
Hunk #7 succeeded at 279.
Hunk #8 succeeded at 289.
Hunk #9 succeeded at 300.
Hunk #10 succeeded at 310.
Hunk #11 succeeded at 329.
Hunk #12 succeeded at 349.
Hunk #13 succeeded at 374.
Hunk #14 succeeded at 404.
Hunk #15 succeeded at 443.
Hunk #16 succeeded at 484.
Hunk #17 succeeded at 501.
Hunk #18 succeeded at 522.
Hunk #19 succeeded at 542.
Hunk #20 succeeded at 553.
Hunk #21 succeeded at 569.
Hunk #22 succeeded at 582.
Hunk #23 succeeded at 614.
Hunk #24 succeeded at 624.
Hunk #25 succeeded at 643.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libssp/configure gcc-9.2.0.new/libssp/configure
|--- gcc-9.2.0.old/libssp/configure	2018-10-31 19:03:16.000000000 +0200
|+++ gcc-9.2.0.new/libssp/configure	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libssp/configure using Plan A...
Hunk #1 succeeded at 5508.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libssp/Makefile.in gcc-9.2.0.new/libssp/Makefile.in
|--- gcc-9.2.0.old/libssp/Makefile.in	2018-10-31 19:03:16.000000000 +0200
|+++ gcc-9.2.0.new/libssp/Makefile.in	2019-08-15 14:56:14.413573842 +0300
--------------------------
Patching file libssp/Makefile.in using Plan A...
Hunk #1 succeeded at 365.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libstdc++-v3/acinclude.m4 gcc-9.2.0.new/libstdc++-v3/acinclude.m4
|--- gcc-9.2.0.old/libstdc++-v3/acinclude.m4	2019-07-04 00:09:13.000000000 +0300
|+++ gcc-9.2.0.new/libstdc++-v3/acinclude.m4	2019-08-15 14:56:14.417573899 +0300
--------------------------
Patching file libstdc++-v3/acinclude.m4 using Plan A...
Hunk #1 succeeded at 800.
Hunk #2 succeeded at 814.
Hunk #3 succeeded at 2411.
Hunk #4 succeeded at 4428.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libstdc++-v3/config/io/basic_file_stdio.cc gcc-9.2.0.new/libstdc++-v3/config/io/basic_file_stdio.cc
|--- gcc-9.2.0.old/libstdc++-v3/config/io/basic_file_stdio.cc	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libstdc++-v3/config/io/basic_file_stdio.cc	2019-08-15 14:56:14.417573899 +0300
--------------------------
Patching file libstdc++-v3/config/io/basic_file_stdio.cc using Plan A...
Hunk #1 succeeded at 362.
Hunk #2 succeeded at 371.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libstdc++-v3/configure gcc-9.2.0.new/libstdc++-v3/configure
|--- gcc-9.2.0.old/libstdc++-v3/configure	2019-07-04 00:09:13.000000000 +0300
|+++ gcc-9.2.0.new/libstdc++-v3/configure	2019-08-15 14:56:14.429574075 +0300
--------------------------
Patching file libstdc++-v3/configure using Plan A...
Hunk #1 succeeded at 6238.
Hunk #2 succeeded at 15426.
Hunk #3 succeeded at 16140.
Hunk #4 succeeded at 66441.
Hunk #5 succeeded at 97748.
Hunk #6 succeeded at 97775.
Hunk #7 succeeded at 99594.
Hunk #8 succeeded at 99608.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libstdc++-v3/crossconfig.m4 gcc-9.2.0.new/libstdc++-v3/crossconfig.m4
|--- gcc-9.2.0.old/libstdc++-v3/crossconfig.m4	2019-03-11 18:28:11.000000000 +0200
|+++ gcc-9.2.0.new/libstdc++-v3/crossconfig.m4	2019-08-15 14:56:14.429574075 +0300
--------------------------
Patching file libstdc++-v3/crossconfig.m4 using Plan A...
Hunk #1 succeeded at 207.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libstdc++-v3/include/bits/locale_classes.h gcc-9.2.0.new/libstdc++-v3/include/bits/locale_classes.h
|--- gcc-9.2.0.old/libstdc++-v3/include/bits/locale_classes.h	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libstdc++-v3/include/bits/locale_classes.h	2019-08-15 14:56:14.429574075 +0300
--------------------------
Patching file libstdc++-v3/include/bits/locale_classes.h using Plan A...
Hunk #1 succeeded at 352.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libstdc++-v3/libsupc++/new_opa.cc gcc-9.2.0.new/libstdc++-v3/libsupc++/new_opa.cc
|--- gcc-9.2.0.old/libstdc++-v3/libsupc++/new_opa.cc	2019-01-01 14:31:55.000000000 +0200
|+++ gcc-9.2.0.new/libstdc++-v3/libsupc++/new_opa.cc	2019-08-15 14:56:14.429574075 +0300
--------------------------
Patching file libstdc++-v3/libsupc++/new_opa.cc using Plan A...
Hunk #1 succeeded at 79.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libstdc++-v3/src/c++98/locale_init.cc gcc-9.2.0.new/libstdc++-v3/src/c++98/locale_init.cc
|--- gcc-9.2.0.old/libstdc++-v3/src/c++98/locale_init.cc	2019-02-19 04:54:42.000000000 +0200
|+++ gcc-9.2.0.new/libstdc++-v3/src/c++98/locale_init.cc	2019-08-15 14:56:14.429574075 +0300
--------------------------
Patching file libstdc++-v3/src/c++98/locale_init.cc using Plan A...
Hunk #1 succeeded at 427.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ruN gcc-9.2.0.old/libstdc++-v3/src/filesystem/ops.cc gcc-9.2.0.new/libstdc++-v3/src/filesystem/ops.cc
|--- gcc-9.2.0.old/libstdc++-v3/src/filesystem/ops.cc	2019-01-17 01:11:10.000000000 +0200
|+++ gcc-9.2.0.new/libstdc++-v3/src/filesystem/ops.cc	2019-08-15 14:56:14.429574075 +0300
--------------------------
Patching file libstdc++-v3/src/filesystem/ops.cc using Plan A...
Hunk #1 succeeded at 119.
done
=> Applying pkgsrc patches for ppc-morphos-gcc-9-9.2.0nb1
=> Verifying /data/pkgsrc/cross/ppc-morphos-gcc-9/patches/patch-gcc_config_rs6000_morphos.c
=> Applying pkgsrc patch /data/pkgsrc/cross/ppc-morphos-gcc-9/patches/patch-gcc_config_rs6000_morphos.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-gcc_config_rs6000_morphos.c,v 1.1 2020/04/14 22:02:21 js Exp $
|
|--- gcc/config/rs6000/morphos.c.orig	2020-01-25 16:25:31.000000000 +0000
|+++ gcc/config/rs6000/morphos.c
--------------------------
Patching file gcc/config/rs6000/morphos.c using Plan A...
Hunk #1 succeeded at 80.
Hunk #2 succeeded at 95.
done
=> Verifying /data/pkgsrc/cross/ppc-morphos-gcc-9/patches/patch-gcc_config_rs6000_rs6000.c
=> Applying pkgsrc patch /data/pkgsrc/cross/ppc-morphos-gcc-9/patches/patch-gcc_config_rs6000_rs6000.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-gcc_config_rs6000_rs6000.c,v 1.1 2020/04/14 22:02:21 js Exp $
|
|Patch by Harry Sintonen.
|
|--- gcc/config/rs6000/rs6000.c.orig	2020-02-09 13:46:53.000000000 +0000
|+++ gcc/config/rs6000/rs6000.c
--------------------------
Patching file gcc/config/rs6000/rs6000.c using Plan A...
Hunk #1 succeeded at 26840.
done
=> Verifying /data/pkgsrc/cross/ppc-morphos-gcc-9/patches/patch-libgcc_crtstuff.c
=> Applying pkgsrc patch /data/pkgsrc/cross/ppc-morphos-gcc-9/patches/patch-libgcc_crtstuff.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libgcc_crtstuff.c,v 1.1 2020/04/14 22:02:21 js Exp $
|
|--- libgcc/crtstuff.c.orig	2020-02-09 13:44:00.000000000 +0000
|+++ libgcc/crtstuff.c
--------------------------
Patching file libgcc/crtstuff.c using Plan A...
Hunk #1 succeeded at 156.
done
=> Verifying /data/pkgsrc/cross/ppc-morphos-gcc-9/patches/patch-libstdc++-v3_libsupc++_unwind-cxx.h
=> Applying pkgsrc patch /data/pkgsrc/cross/ppc-morphos-gcc-9/patches/patch-libstdc++-v3_libsupc++_unwind-cxx.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libstdc++-v3_libsupc++_unwind-cxx.h,v 1.1 2020/04/14 22:02:21 js Exp $
|
|--- libstdc++-v3/libsupc++/unwind-cxx.h.orig	2020-01-25 15:10:52.346666839 +0000
|+++ libstdc++-v3/libsupc++/unwind-cxx.h
--------------------------
Patching file libstdc++-v3/libsupc++/unwind-cxx.h using Plan A...
Hunk #1 succeeded at 37.
done
===> Creating toolchain wrappers for ppc-morphos-gcc-9-9.2.0nb1
===> Configuring for ppc-morphos-gcc-9-9.2.0nb1
=> Modifying GNU configure scripts to avoid --recheck
=> Replacing config-guess with pkgsrc versions
=> Replacing config-sub with pkgsrc versions
=> Replacing install-sh with pkgsrc version
=> Checking for portability problems in extracted files
ERROR: [check-portability.awk] => Found test ... == ...:
ERROR: [check-portability.awk] libgo/mksysinfo.sh:1130: if test "$statfs" == ""; then

Explanation:
===========================================================================
The "test" command, as well as the "[" command, are not required to know
the "==" operator. Only a few implementations like bash and some
versions of ksh support it.

When you run "test foo == foo" on a platform that does not support the
"==" operator, the result will be "false" instead of "true". This can
lead to unexpected behavior.

There are two ways to fix this error message. If the file that contains
the "test ==" is needed for building the package, you should create a
patch for it, replacing the "==" operator with "=". If the file is not
needed, add its name to the CHECK_PORTABILITY_SKIP variable in the
package Makefile.
===========================================================================

*** Error code 1

Stop.
make[1]: stopped in /data/pkgsrc/cross/ppc-morphos-gcc-9
*** Error code 1

Stop.
make: stopped in /data/pkgsrc/cross/ppc-morphos-gcc-9