=> 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 source-highlight-3.1.8.tar.gz
=> Checksum RMD160 OK for source-highlight-3.1.8.tar.gz
=> Checksum SHA512 OK for source-highlight-3.1.8.tar.gz
===> Installing dependencies for source-highlight-3.1.8nb11
=> Tool dependency libtool-base>=2.4.2nb9: found libtool-base-2.4.6nb2
=> Tool dependency gmake>=3.81: found gmake-4.2.1nb1
=> Tool dependency gsed>=3.0.2: found gsed-4.8
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency boost-headers-1.72.*: found boost-headers-1.72.0
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency exctags-[0-9]*: found exctags-5.8nb2
=> Full dependency boost-libs-1.72.*: found boost-libs-1.72.0
=> Full dependency boost-libs>=1.72.0: found boost-libs-1.72.0
===> Overriding tools for source-highlight-3.1.8nb11
===> Extracting for source-highlight-3.1.8nb11
===> Patching for source-highlight-3.1.8nb11
===> Creating toolchain wrappers for source-highlight-3.1.8nb11
===> Configuring for source-highlight-3.1.8nb11
=> 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
=> Adding run-time search paths to pkg-config files.
=> Checking for portability problems in extracted files
ERROR: [check-portability.awk] => Found test ... == ...:
ERROR: [check-portability.awk] lib/tests/valgrind_test.sh.in:62:     if test "$?" == "0"; then
ERROR: [check-portability.awk] lib/tests/valgrind_test.sh.in:72:     if test "$?" == "0"; then
ERROR: [check-portability.awk] lib/tests/valgrind_test.sh.in:81:     if test "x${tmp_err}" == "x"; 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: [check-portability.awk] => Found test ... == ...:
ERROR: [check-portability.awk] tests/valgrind_suppressions.sh.in:58:     if test "$?" == "0"; then
ERROR: [check-portability.awk] tests/valgrind_suppressions.sh.in:68:     if test "$?" == "0"; then
ERROR: [check-portability.awk] tests/valgrind_suppressions.sh.in:77:     if test "x${tmp_err}" == "x"; 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: [check-portability.awk] => Found test ... == ...:
ERROR: [check-portability.awk] tests/valgrind_tests.sh.in:55:     if test "$?" == "0"; then
ERROR: [check-portability.awk] tests/valgrind_tests.sh.in:65:     if test "$?" == "0"; then
ERROR: [check-portability.awk] tests/valgrind_tests.sh.in:74:     if test "x${tmp_err}" == "x"; 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: [check-portability.awk] => Found test ... == ...:
ERROR: [check-portability.awk] tests/valgrind_test.sh.in:62:     if test "$?" == "0"; then
ERROR: [check-portability.awk] tests/valgrind_test.sh.in:72:     if test "$?" == "0"; then
ERROR: [check-portability.awk] tests/valgrind_test.sh.in:81:     if test "x${tmp_err}" == "x"; 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/textproc/source-highlight
*** Error code 1

Stop.
make: stopped in /data/pkgsrc/textproc/source-highlight