=> Bootstrap dependency digest>=20010302: found digest-20190127 WARNING: [license.mk] Every package should define a LICENSE. ===> 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 elmo-1.3.2.tar.gz => Checksum RMD160 OK for elmo-1.3.2.tar.gz => Checksum SHA512 OK for elmo-1.3.2.tar.gz ===> Installing dependencies for elmo-1.3.2nb19 ========================================================================== The following variables will affect the build process of this package, elmo-1.3.2nb19. Their current value is shown below: * CURSES_DEFAULT = curses * SSLBASE = /usr * SSLCERTS = /etc/openssl/certs * SSLDIR = /etc/openssl * SSLKEYS = /etc/openssl/private Based on these variables, the following variables have been set: * CURSES_TYPE = curses 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 checkperms>=1.1: found checkperms-1.12 => Build dependency cwrappers>=20150314: found cwrappers-20180325 => Full dependency gnupg2>=2.2.0: found gnupg2-2.2.20 => Full dependency perl>=5.0: found perl-5.30.2 => Full dependency gpgme>=1.8.0nb1: found gpgme-1.13.1 ===> Overriding tools for elmo-1.3.2nb19 ===> Extracting for elmo-1.3.2nb19 ===> Patching for elmo-1.3.2nb19 => Applying pkgsrc patches for elmo-1.3.2nb19 => Verifying /data/pkgsrc/mail/elmo/patches/patch-aa => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-aa Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aa,v 1.2 2011/12/22 04:33:28 dholland Exp $ | |- newer lex does not define YY_PROTO |- hack around issue with date parsing | |--- src/mlex.l.orig 2004-08-13 11:18:23.000000000 +0000 |+++ src/mlex.l -------------------------- Patching file src/mlex.l using Plan A... Hunk #1 succeeded at 66. Hunk #2 succeeded at 352. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-ab => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-ab Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ab,v 1.2 2008/08/31 20:09:12 dholland Exp $ | |--- src/stats.c.orig 2004-04-29 04:06:10.000000000 -0400 |+++ src/stats.c 2008-08-31 16:01:50.000000000 -0400 -------------------------- Patching file src/stats.c using Plan A... Hunk #1 succeeded at 24. Hunk #2 succeeded at 78. Hunk #3 succeeded at 146. Hunk #4 succeeded at 187. Hunk #5 succeeded at 204. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-ac => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-ac Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ac,v 1.1 2008/08/31 20:09:12 dholland Exp $ | |--- src/mbox.c~ 2004-02-22 16:58:59.000000000 -0500 |+++ src/mbox.c 2008-08-31 15:28:12.000000000 -0400 -------------------------- Patching file src/mbox.c using Plan A... Hunk #1 succeeded at 248. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-ad => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-ad Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ad,v 1.1 2008/08/31 20:09:12 dholland Exp $ | |--- src/mail.c.orig 2004-04-19 16:48:58.000000000 -0400 |+++ src/mail.c 2008-08-31 15:41:26.000000000 -0400 -------------------------- Patching file src/mail.c using Plan A... Hunk #1 succeeded at 28. Hunk #2 succeeded at 102. Hunk #3 succeeded at 126. Hunk #4 succeeded at 880. Hunk #5 succeeded at 888. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-ae => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-ae Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ae,v 1.1 2008/08/31 20:09:12 dholland Exp $ | |--- src/maildir.c~ 2004-08-13 07:18:22.000000000 -0400 |+++ src/maildir.c 2008-08-31 15:32:34.000000000 -0400 -------------------------- Patching file src/maildir.c using Plan A... Hunk #1 succeeded at 347. Hunk #2 succeeded at 369. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-af => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-af Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-af,v 1.1 2008/08/31 20:09:12 dholland Exp $ | |--- configure~ 2004-08-14 08:28:07.000000000 -0400 |+++ configure 2008-08-31 15:39:09.000000000 -0400 -------------------------- Patching file configure using Plan A... Hunk #1 succeeded at 11282. Hunk #2 succeeded at 11398. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-ag => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-ag Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ag,v 1.1 2008/08/31 20:09:12 dholland Exp $ | |--- src/mime.c~ 2004-08-13 07:18:22.000000000 -0400 |+++ src/mime.c 2008-08-31 15:50:42.000000000 -0400 -------------------------- Patching file src/mime.c using Plan A... Hunk #1 succeeded at 526. Hunk #2 succeeded at 558. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-ah => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-ah Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ah,v 1.1 2008/08/31 20:09:12 dholland Exp $ | |--- src/sender.c~ 2004-08-13 07:18:23.000000000 -0400 |+++ src/sender.c 2008-08-31 15:53:02.000000000 -0400 -------------------------- Patching file src/sender.c using Plan A... Hunk #1 succeeded at 178. Hunk #2 succeeded at 206. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-ai => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-ai Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ai,v 1.1 2008/08/31 20:09:12 dholland Exp $ | |--- src/bayes.c~ 2004-04-29 04:06:13.000000000 -0400 |+++ src/bayes.c 2008-08-31 15:56:54.000000000 -0400 -------------------------- Patching file src/bayes.c using Plan A... Hunk #1 succeeded at 32. Hunk #2 succeeded at 223. Hunk #3 succeeded at 301. Hunk #4 succeeded at 341. Hunk #5 succeeded at 375. Hunk #6 succeeded at 542. Hunk #7 succeeded at 556. Hunk #8 succeeded at 610. Hunk #9 succeeded at 653. Hunk #10 succeeded at 670. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-aj => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-aj Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aj,v 1.1 2008/08/31 20:09:12 dholland Exp $ | |--- src/procmail.c~ 2004-08-13 07:18:23.000000000 -0400 |+++ src/procmail.c 2008-08-31 16:00:25.000000000 -0400 -------------------------- Patching file src/procmail.c using Plan A... Hunk #1 succeeded at 111. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-src_compose_l => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-src_compose_l Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_compose_l,v 1.1 2011/12/22 04:33:28 dholland Exp $ | |- newer lex does not define YY_PROTO | |--- src/compose.l~ 2004-08-13 11:18:22.000000000 +0000 |+++ src/compose.l -------------------------- Patching file src/compose.l using Plan A... Hunk #1 succeeded at 83. done => Verifying /data/pkgsrc/mail/elmo/patches/patch-src_confread_l => Applying pkgsrc patch /data/pkgsrc/mail/elmo/patches/patch-src_confread_l Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_confread_l,v 1.1 2011/12/22 04:33:28 dholland Exp $ | |- newer lex does not define YY_PROTO | |--- src/confread.l~ 2004-08-13 11:18:22.000000000 +0000 |+++ src/confread.l -------------------------- Patching file src/confread.l using Plan A... Hunk #1 succeeded at 64. done ===> Creating toolchain wrappers for elmo-1.3.2nb19 ===> Configuring for elmo-1.3.2nb19 => 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 => Replacing Perl interpreter in src/elmoconf.pl. => Fixing locale directory references. INFO: [subst.mk:pkglocaledir] Nothing changed in ./Makefile.in. INFO: [subst.mk:pkglocaledir] Nothing changed in ./doc/Makefile.in. INFO: [subst.mk:pkglocaledir] Nothing changed in ./src/Makefile.in. INFO: [subst.mk:pkglocaledir] Nothing changed in ./themes/Makefile.in. => Checking for portability problems in extracted files ERROR: [check-portability.awk] => Found test ... == ...: ERROR: [check-portability.awk] configure.in:66: if test "$GPGME4" == "no" ; then ERROR: [check-portability.awk] configure.in:72: else if test "$GPGME4" == "yes" ; 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/mail/elmo *** Error code 1 Stop. make: stopped in /data/pkgsrc/mail/elmo