=> 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 yaws-2.0.6.tar.gz
=> Checksum RMD160 OK for yaws-2.0.6.tar.gz
=> Checksum SHA512 OK for yaws-2.0.6.tar.gz
===> Installing dependencies for yaws-2.0.6nb2
==========================================================================
The following variables will affect the build process of this package,
yaws-2.0.6nb2.  Their current value is shown below:

        * PAM_DEFAULT = openpam
        * VARBASE = /var

Based on these variables, the following variables have been set:

        * PAMBASE (defined, but empty)

You may want to abort the process now with CTRL-C and change their value
before continuing.  Be sure to run `/usr/bin/make clean' after
the changes.
==========================================================================
=> 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 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 erlang>=18.0: found erlang-22.2.8
===> Overriding tools for yaws-2.0.6nb2
===> Extracting for yaws-2.0.6nb2
cd /data/scratch/www/yaws/work/yaws-2.0.6 && /bin/chmod -R g-w www
/bin/rm -Rf /data/scratch/www/yaws/work/yaws-2.0.6/www/testdir
===> Patching for yaws-2.0.6nb2
=> Applying pkgsrc patches for yaws-2.0.6nb2
=> Verifying /data/pkgsrc/www/yaws/patches/patch-ai
=> Applying pkgsrc patch /data/pkgsrc/www/yaws/patches/patch-ai
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ai,v 1.2 2018/04/13 16:12:13 fhajny Exp $
|
|Replace '%var%' with '@VAR@'
|
|--- scripts/netbsd/yaws.sh.orig	2018-04-10 10:32:09.000000000 +0000
|+++ scripts/netbsd/yaws.sh
--------------------------
Patching file scripts/netbsd/yaws.sh using Plan A...
Hunk #1 succeeded at 1.
Hunk #2 succeeded at 18.
Hunk #3 succeeded at 35.
done
=> Verifying /data/pkgsrc/www/yaws/patches/patch-scripts_yaws.template
=> Applying pkgsrc patch /data/pkgsrc/www/yaws/patches/patch-scripts_yaws.template
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-scripts_yaws.template,v 1.1 2018/04/13 16:12:13 fhajny Exp $
|
|Portability.
|
|--- scripts/yaws.template.orig	2018-04-10 10:32:09.000000000 +0000
|+++ scripts/yaws.template
--------------------------
Patching file scripts/yaws.template using Plan A...
Hunk #1 succeeded at 399.
done
===> Creating toolchain wrappers for yaws-2.0.6nb2
===> Configuring for yaws-2.0.6nb2
=> 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] scripts/Makefile.in:553: @MINGW_FALSE@	if [ $${user} == 'root' -o $${user} != $$(whoami) ]; 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] testsuite/run_common_test.in:116:         if test $failures == 0; 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/www/yaws
*** Error code 1

Stop.
make: stopped in /data/pkgsrc/www/yaws