=> Bootstrap dependency digest>=20010302: found digest-20111104
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 nocol-4.3.1.tar.gz
=> Checksum RMD160 OK for nocol-4.3.1.tar.gz
===> Installing dependencies for nocol-4.3.1nb5
=> Build dependency libtool-base>=2.2.6bnb3: found libtool-base-2.2.6bnb6
=> Build dependency imake-[0-9]*: found imake-1.0.3nb1
=> Build dependency checkperms>=1.1: found checkperms-1.11
=> Full dependency tk-Tix-[0-9]*: found tk-Tix-8.2.0b1nb3
=> Full dependency perl>=5.0: found perl-5.14.2nb5
===> Overriding tools for nocol-4.3.1nb5
===> Extracting for nocol-4.3.1nb5
===> Patching for nocol-4.3.1nb5
=> Applying pkgsrc patches for nocol-4.3.1nb5
===> Creating toolchain wrappers for nocol-4.3.1nb5
===> Configuring for nocol-4.3.1nb5
=> Replacing tk-Tix interpreter in tknocol/tkNocol.tix.
=> Replacing Perl interpreter in perlnocol/hostmon-osclients/hostmon-client*.
=> Checking for portability problems in extracted files

SET INSTALLATION DIRECTORY
 It is advisable to put all the NOCOL files under one directory
 tree with further sub-directories like bin/ etc/ lib/ man/
 This will allow easy upgrades and replacements of this software
 without leaving old unsed files lying around.

 However, the DATA and LOG directories will have files which are constantly
 updated by the monitors, and you might want to keep them separately under
 a VAR directory (or alternately create soft links to these directories).
Enter top level directory [/usr/local/nocol]: Enter location of man pages [/usr/pkg/man]: Enter extension for man pages [n]:                SELECT A LOGHOST
 The various monitors will log messages to a loghost. It might
 be useful to create a CNAME entry for nocol.your.domain...
Enter FULLY QUALIFIED name of your loghost [neuromancer]: 
 NOCOL sends regular operational email messages when a device goes
 critical, etc. It is advised to create a "nocol-ops" email alias in
 your mail system.
 It also needs to send critical messages (in case of wrong directory
 permissions, etc.) - preferably to a system administrator. An email 
 alias such as "nocol-critical" sounds right.

Where is your MAIL program located? [/usr/bin/mail] :Where should the operational email go? [nocol-ops@neuromancer] :Where should urgent/critical email go? [nocol-crit@neuromancer] :
Which compiler would you like to use? [gcc]: What compiler options do you want (-DDEBUG)? [-O]: If using a yacc alternate, enter it here (bison -y) [yacc]: Where is PERL located on your system? [/bin/perl]: 
Detecting operating system dependencies for NetBSD 6.0_BETA...
     OS=NetBSD 6.0_BETA is not a supported or detected operating system. Try setting
     the value of OS manually to the type of your system or set the
     OS_CFLAGS and OS_LIBS value manually in the Makefile if compile fails.

        OS_CFLAGS = 
        OS_LIBS   = 

Saving all values in config.cache...
Editing various Makefiles...

Done editing Makefiles.

              Type   "make"  to start building  NOCOL

=> Modifying libtool scripts to use pkgsrc libtool