=> Bootstrap dependency digest>=20010302: found digest-20210928 WARNING: [license.mk] Every package should define a LICENSE. => Checksum SHA1 OK for wwwcount2.5.tar.gz => Checksum RMD160 OK for wwwcount2.5.tar.gz => Checksum SHA512 OK for wwwcount2.5.tar.gz ===> Installing dependencies for wwwcount-2.5nb2 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Build dependency cwrappers>=20150314: found cwrappers-20180325 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Overriding tools for wwwcount-2.5nb2 ===> Extracting for wwwcount-2.5nb2 ===> Patching for wwwcount-2.5nb2 => Applying pkgsrc patches for wwwcount-2.5nb2 => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/wwwcount/patches/patch-aa => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/wwwcount/patches/patch-aa Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aa,v 1.5 2006/07/19 19:48:21 jlam Exp $ | |--- Count-config.orig 1999-01-03 15:07:58.000000000 -0800 |+++ Count-config -------------------------- Patching file Count-config using Plan A... Hunk #1 succeeded at 20. Hunk #2 succeeded at 35. Hunk #3 succeeded at 117. Hunk #4 succeeded at 376. Hunk #5 succeeded at 518. Hunk #6 succeeded at 546. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/wwwcount/patches/patch-ab => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/wwwcount/patches/patch-ab Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ab,v 1.3 1999/05/14 23:23:58 tron Exp $ | |--- configure.orig Sun Jan 24 20:49:38 1999 |+++ configure Sat May 15 01:12:06 1999 -------------------------- Patching file configure using Plan A... Hunk #1 succeeded at 1573. done => Verifying /amd/pkgsrc/CHROOT/P/pkgsrc/www/wwwcount/patches/patch-ae => Applying pkgsrc patch /amd/pkgsrc/CHROOT/P/pkgsrc/www/wwwcount/patches/patch-ae Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ae,v 1.5 2010/06/27 19:16:03 joerg Exp $ | |--- Count-install.orig 1999-05-17 01:01:50.000000000 +0000 |+++ Count-install -------------------------- Patching file Count-install using Plan A... Hunk #1 succeeded at 13. Hunk #2 succeeded at 27. Hunk #3 succeeded at 112. Hunk #4 succeeded at 180. Hunk #5 succeeded at 194. Hunk #6 succeeded at 235. Hunk #7 succeeded at 254. Hunk #8 succeeded at 278. Hunk #9 succeeded at 300. Hunk #10 succeeded at 353. Hunk #11 succeeded at 365. Hunk #12 succeeded at 415. done ===> Creating toolchain wrappers for wwwcount-2.5nb2 ===> Configuring for wwwcount-2.5nb2 cd /tmp/www/wwwcount/work/wwwcount2.5; PREFIX=/usr/pkg PKG_SYSCONFDIR=/usr/pkg/etc VARBASE=/var ./Count-config < /dev/null Welcome to the configuration procedure of Count 2.5 --------------------------------------------------- o You must know where your system keeps CGI programs (cgi-bin directory) It is necessary to generate the install program. This directory must exist. If this directory does not exist, the configuration procedure will Abort! o You have to decide a directory, where you will keep all counter related stuff. This directory will have other directories inside. Default values will be supplied, press Return key to accept the default value. Try to Accept the default value, it will make your life much easier, because not much error checking is done to verify input. During installation, the directories will be created for you if they do not exist and if you have the permission to do so. ++ Continue [y|n]? You need to enter the full path of the directory where you system keeps the CGI programs. *cgi-bin directory [/usr/pkg/libexec/cgi-bin]: WARNING: Directory "/usr/pkg/libexec/cgi-bin" does not exist! If you do not know where your system keeps CGI programs, find it out first. If you did not configure your http server yet, please do so and come back! Presss Control-C to exit, any key to continue You need to enter the base directory of the counter related stuff. It must be a absolute path. *Base directory [/usr/pkg/etc]: You need to enter the name directory of the configuration file. * Config directory [/usr/pkg/etc]: You need to enter the name of the configuration file. Note, it is not the path of the file, just the name. No / is allowed in the name. This file contains the information about o if you want to ignore access from certain hosts o host access authentication You will create this file later by running the program "Gen_conf". * Name of the configuration file [wwwcount.conf]: You need to enter the directory of the counter data file. *Data directory [/var/db/wwwcount]: You need to enter the directory of digits *Digits directory [/usr/pkg/libdata/wwwcount/digits]: You need to enter the directory of the Log file. *Log directory [/var/log]: You need to enter the name of the Log file. Note, it just a name, not the path. No / is allowed in the name. This file hold the error messages of the counter. It also logs if someone tried to access your counter remotely. * Name of the log file [wwwcount]: Your configuration: ---------------------------------------------------------------- CgiBinDir=/usr/pkg/libexec/cgi-bin BaseDir= /usr/pkg/etc DigitDir=/usr/pkg/libdata/wwwcount/digits ConfDir= /usr/pkg/etc ConfFile=wwwcount.conf DataDir=/var/db/wwwcount LogDir=/var/log LogFile=wwwcount ---------------------------------------------------------------- Everything looks OK [y|n]? Great! creating header file src/config.h creating variables template file ./Config.tmpl for the install program.. => 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 creating cache ./config.cache checking whether make sets ${MAKE}... yes checking for gcc... gcc checking whether the C compiler (gcc -O2 -fPIC -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,-R/usr/pkg/lib) works... yes checking whether the C compiler (gcc -O2 -fPIC -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,-R/usr/pkg/lib) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking for ranlib... ranlib checking host system type... x86_64--netbsd checking target system type... x86_64--netbsd checking build system type... x86_64--netbsd checking host system type... x86_64--netbsd checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking whether time.h and sys/time.h may both be included... yes checking for string.h... yes checking for fcntl.h... yes checking for memory.h... yes checking for malloc.h... yes checking for unistd.h... yes checking for ctype.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/param.h... yes checking for sys/file.h... yes checking for stdlib.h... yes checking for working const... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for flock... yes checking for strcasecmp... yes checking for mktime... yes checking for strftime... yes checking for gmtime... yes checking for system type... updating cache ./config.cache creating ./config.status creating libs/mcfg/Makefile creating libs/bigplus/Makefile creating libs/combine/Makefile creating utils/mkstrip/Makefile creating utils/extdgts/Makefile creating src/Makefile