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

        * JPEG_DEFAULT = jpeg

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

        * JPEGBASE (defined, but empty)
        * JPEG_TYPE = jpeg

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 gmake>=3.81: found gmake-4.2.1nb1
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency xorgproto>=2016.1: found xorgproto-2019.2nb3
=> Build dependency xcb-proto>=1.4: found xcb-proto-1.14
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency libpaper>=1.1.22: found libpaper-1.1.28
=> Full dependency fltk>=1.3.3nb4: found fltk-1.3.5
===> Overriding tools for tuxpaint-config-0.0.14
===> Extracting for tuxpaint-config-0.0.14
===> Patching for tuxpaint-config-0.0.14
=> Applying pkgsrc patches for tuxpaint-config-0.0.14
=> Verifying /data/pkgsrc/graphics/tuxpaint-config/patches/patch-Makefile
=> Applying pkgsrc patch /data/pkgsrc/graphics/tuxpaint-config/patches/patch-Makefile
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-Makefile,v 1.1 2019/12/19 22:17:33 joerg Exp $
|
|Ensure that trans directory is made before trying to put files in it.
|
|--- Makefile.orig	2019-12-19 18:27:04.435743784 +0000
|+++ Makefile
--------------------------
Patching file Makefile using Plan A...
Hunk #1 succeeded at 406.
done
===> Creating toolchain wrappers for tuxpaint-config-0.0.14
===> Configuring for tuxpaint-config-0.0.14
=> Checking for portability problems in extracted files
ERROR: [check-portability.awk] => Found test ... == ...:
ERROR: [check-portability.awk] Makefile:168: 		ARCH_LINKS=$(shell if [ "x$$OSTYPE" == "xcygwin" ]; then echo -n "-lintl"; else echo -n "-lintl-8"; fi ) \
ERROR: [check-portability.awk] Makefile:179: 		ARCH_LINKS=$(shell if [ "x$$OSTYPE" == "xcygwin" ]; then echo -n "-lintl"; else echo -n "-lintl-8"; fi ) \

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/graphics/tuxpaint-config
*** Error code 1

Stop.
make: stopped in /data/pkgsrc/graphics/tuxpaint-config