=> Bootstrap dependency digest>=20010302: found digest-20190127
=> Checksum SHA1 OK for phoronix-test-suite-8.8.1.tar.gz
=> Checksum RMD160 OK for phoronix-test-suite-8.8.1.tar.gz
=> Checksum SHA512 OK for phoronix-test-suite-8.8.1.tar.gz
===> Installing dependencies for phoronix-test-suite-8.8.1nb1
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency php73-curl>=5.3: found php73-curl-7.3.22nb9
=> Full dependency php73-gd>=5.3: found php73-gd-7.3.22nb1
=> Full dependency php73-json>=5.3: found php73-json-7.3.22
=> Full dependency php73-pcntl>=5.3: found php73-pcntl-7.3.22
=> Full dependency php73-posix>=5.3: found php73-posix-7.3.22
=> Full dependency php73-zip>=5.3: found php73-zip-7.3.22nb4
=> Full dependency php73-zlib>=5.3: found php73-zlib-7.3.22nb1
=> Full dependency php>=7.3.18nb1<7.3.99: found php-7.3.22
=> Full dependency shared-mime-info>=1.0nb1: found shared-mime-info-1.10nb2
=> Full dependency hicolor-icon-theme>=0.9nb1: found hicolor-icon-theme-0.17
=> Full dependency desktop-file-utils>=0.10nb1: found desktop-file-utils-0.26
===> 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'.
===> Overriding tools for phoronix-test-suite-8.8.1nb1
===> Extracting for phoronix-test-suite-8.8.1nb1
===> Patching for phoronix-test-suite-8.8.1nb1
=> Applying pkgsrc patches for phoronix-test-suite-8.8.1nb1
=> Verifying /data/pkgsrc/benchmarks/phoronix-test-suite/patches/patch-install-sh
=> Applying pkgsrc patch /data/pkgsrc/benchmarks/phoronix-test-suite/patches/patch-install-sh
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-install-sh,v 1.4 2019/06/10 02:48:23 jym Exp $
|
|* Handle pkgsrc hierarchy especially paths to man pages;
|* pkgsrc will handle the MIME and desktopdb updates. No need to ask user
|  to do it manually afterwards;
|* Change "cp -r" to "cp -R". OpenGroup deprecated -r, and -R is the only
|  reliable portable option;
|* Remove the systemd directory creation and make the PLIST handle
|  the presence/absence of systemd ecosystem.
|
|$NetBSD: patch-install-sh,v 1.4 2019/06/10 02:48:23 jym Exp $
|
|--- install-sh.orig	2019-05-30 15:01:30.000000000 +0000
|+++ install-sh
--------------------------
Patching file install-sh using Plan A...
Hunk #1 succeeded at 53.
Hunk #2 succeeded at 64.
Hunk #3 succeeded at 119.
done
===> Creating toolchain wrappers for phoronix-test-suite-8.8.1nb1
===> Configuring for phoronix-test-suite-8.8.1nb1
=> Checking for portability problems in extracted files
ERROR: [check-portability.awk] => Found test ... == ...:
ERROR: [check-portability.awk] pts-core/static/sample-pts-client-update-script.sh:23: if [ "$GIT_COMMIT_TO_USE" != "$CURRENT_GIT_COMMIT" ] || [ "$FRESH_CLONE" == "1" ]

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/benchmarks/phoronix-test-suite
*** Error code 1

Stop.
make: stopped in /data/pkgsrc/benchmarks/phoronix-test-suite