=> Bootstrap dependency digest>=20010302: found digest-20121220
=> Checksum SHA1 OK for swig-2.0.9.tar.gz
=> Checksum RMD160 OK for swig-2.0.9.tar.gz
===> Installing dependencies for swig-2.0.9
=> Tool dependency libtool-base>=2.2.6bnb3: found libtool-base-2.4.2nb3
=> Tool dependency gmake>=3.81: found gmake-3.82nb7
=> Tool dependency checkperms>=1.1: found checkperms-1.11
=> Full dependency pcre>=8.30nb1: found pcre-8.33
===> Overriding tools for swig-2.0.9
===> Extracting for swig-2.0.9
===> Patching for swig-2.0.9
===> Creating toolchain wrappers for swig-2.0.9
===> Configuring for swig-2.0.9
=> 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] configure: 	if test x"$RUBYDIR" == x"" || test x"$RUBYDIR" == x"nil"; then
ERROR: [check-portability.awk] configure: 	if test x"$RUBYDIR" == x"" || test x"$RUBYDIR" == x"nil"; 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: stopped in /usr/pkgsrc/wip/swig2
*** Error code 1

Stop.
make: stopped in /usr/pkgsrc/wip/swig2