+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PKG_APACHE=apache24 WRKLOG=/tmp/bulklog/xymon-4.3.30nb12/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent PKG_APACHE=apache24 WRKLOG=/tmp/bulklog/xymon-4.3.30nb12/work.log
=> Bootstrap dependency digest>=20211023: found digest-20220214
=> Checksum BLAKE2s OK for xymon-4.3.30.tar.gz
=> Checksum SHA512 OK for xymon-4.3.30.tar.gz
===> Installing dependencies for xymon-4.3.30nb12
==========================================================================
The supported build options for xymon are:
ldap snmp ssl
The currently selected options are:
ldap ssl
You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or the following variable. Its current value is shown:
PKG_OPTIONS.xymon (not defined)
==========================================================================
==========================================================================
The following variables will affect the build process of this package,
xymon-4.3.30nb12. Their current value is shown below:
* PKG_APACHE_DEFAULT = apache24
* SSLBASE (defined)
* SSLCERTBUNDLE (not defined)
* SSLCERTS = /opt/pkg/etc/xymon/openssl/certs
* SSLDIR = /opt/pkg/etc/xymon/openssl
* SSLKEYS = /opt/pkg/etc/xymon/openssl/private
* VARBASE = /var/opt/pkg
* XYMONHOSTURL = /
* XYMONSERVERIP = 127.0.0.1
* XYMONSERVERNAME = "`uname -n`"
Based on these variables, the following variables have been set:
* APACHE_PKG_PREFIX = ap24
* PKG_APACHE = apache24
You may want to abort the process now with CTRL-C and change the value
of variables in the first group before continuing. Be sure to run
`/opt/pkg/bin/bmake clean' after the changes.
==========================================================================
=> Tool dependency glib2-tools-[0-9]*: found glib2-tools-2.78.4
=> Tool dependency mktools-[0-9]*: found mktools-20220614
=> Tool dependency gmake>=3.81: found gmake-4.4.1
=> Tool dependency perl>=5.0: found perl-5.38.2
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency xorgproto>=2016.1: found xorgproto-2023.2
=> Build dependency xcb-proto>=1.15.2nb3: found xcb-proto-1.16.0nb1
=> Full dependency fping>=2: found fping-5.1
=> Full dependency xymonclient-4.3.30{,nb*}: found xymonclient-4.3.30nb1
=> Full dependency openldap-client>=2.6.6nb1: found openldap-client-2.6.7
=> Full dependency openssl>=3: found openssl-3.1.5
=> Full dependency rrdtool>=1.8.0nb7: found rrdtool-1.8.0nb7
=> Full dependency png>=1.6.0nb1: found png-1.6.42
=> Full dependency pcre>=8.30nb1: found pcre-8.45
=> Full dependency libcares>=1.6.0: found libcares-1.27.0
=> Full dependency apache>=2.4.58nb1<2.5: found apache-2.4.58nb2
===> Overriding tools for xymon-4.3.30nb12
===> Extracting for xymon-4.3.30nb12
===> Patching for xymon-4.3.30nb12
=> Applying pkgsrc patches for xymon-4.3.30nb12
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-aa
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-aa
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aa,v 1.6 2022/12/07 08:15:59 jperkin Exp $
|
|add extra options for cases where PREFIX is not in a standard location
|
|add INSTALLEXADIR for some pkgsrc magic
|
|$NetBSD: patch-aa,v 1.6 2022/12/07 08:15:59 jperkin Exp $
|
|--- configure.server.orig 2019-04-22 18:20:02.000000000 +0000
|+++ configure.server
--------------------------
Patching file configure.server using Plan A...
Hunk #1 succeeded at 17.
Hunk #2 succeeded at 27.
Hunk #3 succeeded at 41.
Hunk #4 succeeded at 71.
Hunk #5 succeeded at 416.
Hunk #6 succeeded at 467.
Hunk #7 succeeded at 545.
Hunk #8 succeeded at 576.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ab
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ab
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ab,v 1.5 2014/02/27 20:22:41 spz Exp $
|
|add SNMPCONFIG var for non-standard PREFIX
|add lots of pkgsrc magic
|
|--- build/Makefile.rules.orig 2014-02-13 09:00:40.000000000 +0000
|+++ build/Makefile.rules
--------------------------
Patching file build/Makefile.rules using Plan A...
Hunk #1 succeeded at 24.
Hunk #2 succeeded at 38.
Hunk #3 succeeded at 103 (offset 1 line).
Hunk #4 succeeded at 176 (offset 1 line).
Hunk #5 succeeded at 184 (offset 1 line).
Hunk #6 succeeded at 254 (offset 1 line).
Hunk #7 succeeded at 315 (offset 1 line).
Hunk #8 succeeded at 348 (offset 1 line).
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ac
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ac
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ac,v 1.6 2017/09/28 10:40:35 spz Exp $
|
|pkgsrc uses rc.d files to stop/start, don't copy that xymon.sh
|allow hardening
|
|--- xymond/Makefile.orig 2015-03-13 06:15:38.000000000 +0000
|+++ xymond/Makefile
--------------------------
Patching file xymond/Makefile using Plan A...
Hunk #1 succeeded at 41.
Hunk #2 succeeded at 74.
Hunk #3 succeeded at 98.
Hunk #4 succeeded at 187.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ad
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ad
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ad,v 1.7 2017/09/28 10:40:35 spz Exp $
|
|- netbsd has stdint.h
|- remove stray commas
|- make sure hardening flags can be inherited
|
|--- build/Makefile.NetBSD.orig 2012-08-01 08:48:15.000000000 +0000
|+++ build/Makefile.NetBSD
--------------------------
Patching file build/Makefile.NetBSD using Plan A...
Hunk #1 succeeded at 1.
Hunk #2 succeeded at 11.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ae
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ae
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ae,v 1.3 2012/10/11 18:42:19 spz Exp $
|
|allow setting the path to wc and df via environment variable WC and DF,
|respectively
|
|--- build/bb-commands.sh.orig 2011-03-08 17:20:28.000000000 +0000
|+++ build/bb-commands.sh
--------------------------
Patching file build/bb-commands.sh using Plan A...
Hunk #1 succeeded at 9.
Hunk #2 succeeded at 36.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-af
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-af
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-af,v 1.3 2011/10/16 15:19:09 spz Exp $
|
|xymonclient starts from rc.d, don't start it via xymon also
|
|--- xymond/etcfiles/tasks.cfg.DIST.orig 2011-03-08 17:20:28.000000000 +0000
|+++ xymond/etcfiles/tasks.cfg.DIST
--------------------------
Patching file xymond/etcfiles/tasks.cfg.DIST using Plan A...
Hunk #1 succeeded at 193 (offset 13 lines).
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ah
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-ah
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ah,v 1.4 2017/09/28 10:40:35 spz Exp $
|
|the c-ares dependencies are being difficult, manipulate it into working
|
|use a variable for the path to net-snmp-config, for cases with nonstandard
|locations
|
|allow hardening
|
|--- xymonnet/Makefile.orig 2015-02-26 07:41:56.000000000 +0000
|+++ xymonnet/Makefile
--------------------------
Patching file xymonnet/Makefile using Plan A...
Hunk #1 succeeded at 30.
Hunk #2 succeeded at 71.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.AIX
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.AIX
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.AIX,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|make sure hardening flags can be inherited
|
|--- build/Makefile.AIX.orig 2011-03-08 17:20:28.000000000 +0000
|+++ build/Makefile.AIX
--------------------------
Patching file build/Makefile.AIX using Plan A...
Hunk #1 succeeded at 12.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.Darwin
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.Darwin
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.Darwin,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|make sure hardening flags can be inherited
|
|--- build/Makefile.Darwin.orig 2012-08-01 08:48:15.000000000 +0000
|+++ build/Makefile.Darwin
--------------------------
Patching file build/Makefile.Darwin using Plan A...
Hunk #1 succeeded at 10.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.FreeBSD
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.FreeBSD
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.FreeBSD,v 1.2 2017/09/28 10:40:35 spz Exp $
|
|FreeBSD has stdint.h
|make sure hardening flags can be inherited
|
|--- build/Makefile.FreeBSD.orig 2014-01-07 08:43:44.000000000 +0000
|+++ build/Makefile.FreeBSD
--------------------------
Patching file build/Makefile.FreeBSD using Plan A...
Hunk #1 succeeded at 1.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.HP-UX
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.HP-UX
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.HP-UX,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|make sure hardening flags can be inherited
|
|--- build/Makefile.HP-UX.orig 2012-08-01 08:48:15.000000000 +0000
|+++ build/Makefile.HP-UX
--------------------------
Patching file build/Makefile.HP-UX using Plan A...
Hunk #1 succeeded at 19.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.IRIX
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.IRIX
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.IRIX,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|make sure hardening flags can be inherited
|
|--- build/Makefile.IRIX.orig 2011-03-08 17:20:28.000000000 +0000
|+++ build/Makefile.IRIX
--------------------------
Patching file build/Makefile.IRIX using Plan A...
Hunk #1 succeeded at 8.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.Linux
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.Linux
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.Linux,v 1.3 2019/11/24 20:16:55 spz Exp $
|
|--- build/Makefile.Linux.orig 2019-03-11 23:17:41.000000000 +0000
|+++ build/Makefile.Linux
--------------------------
Patching file build/Makefile.Linux using Plan A...
Hunk #1 succeeded at 5.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.OSF1
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.OSF1
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.OSF1,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|make sure hardening flags can be inherited
|
|--- build/Makefile.OSF1.orig 2011-03-08 17:20:28.000000000 +0000
|+++ build/Makefile.OSF1
--------------------------
Patching file build/Makefile.OSF1 using Plan A...
Hunk #1 succeeded at 8.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.OSX
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.OSX
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.OSX,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|make sure hardening flags can be inherited
|
|--- build/Makefile.OSX.orig 2011-03-08 17:20:28.000000000 +0000
|+++ build/Makefile.OSX
--------------------------
Patching file build/Makefile.OSX using Plan A...
Hunk #1 succeeded at 6.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.OpenBSD
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.OpenBSD
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.OpenBSD,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|make sure hardening flags can be inherited
|
|--- build/Makefile.OpenBSD.orig 2012-07-31 13:50:31.000000000 +0000
|+++ build/Makefile.OpenBSD
--------------------------
Patching file build/Makefile.OpenBSD using Plan A...
Hunk #1 succeeded at 9.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.SunOS
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.SunOS
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.SunOS,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|make sure hardening flags can be inherited
|
|--- build/Makefile.SunOS.orig 2012-08-01 08:48:15.000000000 +0000
|+++ build/Makefile.SunOS
--------------------------
Patching file build/Makefile.SunOS using Plan A...
Hunk #1 succeeded at 9.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.generic
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_Makefile.generic
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_Makefile.generic,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|make sure hardening flags can be inherited
|
|--- build/Makefile.generic.orig 2011-03-08 17:20:28.000000000 +0000
|+++ build/Makefile.generic
--------------------------
Patching file build/Makefile.generic using Plan A...
Hunk #1 succeeded at 8.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_rrd.sh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_rrd.sh
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_rrd.sh,v 1.3 2012/10/11 18:42:19 spz Exp $
|
|make it possible to deal with nonstandard locations of libpng* and libz*
|
|--- build/rrd.sh.orig 2012-07-31 13:51:12.000000000 +0000
|+++ build/rrd.sh
--------------------------
Patching file build/rrd.sh using Plan A...
Hunk #1 succeeded at 70.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_snmp.sh
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-build_snmp.sh
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-build_snmp.sh,v 1.1 2011/10/16 15:19:09 spz Exp $
|
|make it possible to deal with a net-snmp-config that's not in the default path
|
|--- build/snmp.sh.orig 2008-09-30 16:37:31.000000000 +0000
|+++ build/snmp.sh
--------------------------
Patching file build/snmp.sh using Plan A...
Hunk #1 succeeded at 2.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-common_Makefile
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-common_Makefile
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-common_Makefile,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|allow hardening
|
|--- common/Makefile.orig 2014-01-19 12:17:56.000000000 +0000
|+++ common/Makefile
--------------------------
Patching file common/Makefile using Plan A...
Hunk #1 succeeded at 28.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-configure
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-configure
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-configure,v 1.5 2017/09/28 10:40:35 spz Exp $
|
|Make sure the toplevel configure script exits on failure.
|
|--- configure.orig 2014-09-28 09:39:28.000000000 +0000
|+++ configure
--------------------------
Patching file configure using Plan A...
Hunk #1 succeeded at 14.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-web_Makefile
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-web_Makefile
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-web_Makefile,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|allow hardening
|
|--- web/Makefile.orig 2015-11-01 18:17:08.000000000 +0000
|+++ web/Makefile
--------------------------
Patching file web/Makefile using Plan A...
Hunk #1 succeeded at 57.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-xymond_client_netbsd.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-xymond_client_netbsd.c
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xymond_client_netbsd.c,v 1.2 2014/09/21 14:49:45 spz Exp $
|
|--- xymond/client/netbsd.c.orig 2012-07-14 16:32:11.000000000 +0000
|+++ xymond/client/netbsd.c
--------------------------
Patching file xymond/client/netbsd.c using Plan A...
Hunk #1 succeeded at 24.
Hunk #2 succeeded at 48.
Hunk #3 succeeded at 59.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-xymond_rrd_do__disk.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-xymond_rrd_do__disk.c
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xymond_rrd_do__disk.c,v 1.1 2014/09/21 14:49:45 spz Exp $
|
|BSDish systems' df -i retains the block stats, so you'd want 8, 7 and 5.
|Fortunately, counting from behind instead works out.
|This also fits AIX if you are using df -v.
|
|--- xymond/rrd/do_disk.c.orig 2012-07-13 14:05:20.000000000 +0000
|+++ xymond/rrd/do_disk.c 2014-09-21 13:52:45.000000000 +0000
--------------------------
Patching file xymond/rrd/do_disk.c using Plan A...
Hunk #1 succeeded at 139.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-xymond_rrd_do__vmstat.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-xymond_rrd_do__vmstat.c
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xymond_rrd_do__vmstat.c,v 1.1 2011/11/16 21:12:35 spz Exp $
|
|at least NetBSD 4-5.99 vmstat gives you two disks if you don't specify any,
|no matter how many you actually have
|
|--- xymond/rrd/do_vmstat.c.orig 2011-07-31 21:01:52.000000000 +0000
|+++ xymond/rrd/do_vmstat.c
--------------------------
Patching file xymond/rrd/do_vmstat.c using Plan A...
Hunk #1 succeeded at 180 (offset 26 lines).
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-xymonproxy_Makefile
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/net/xymon/patches/patch-xymonproxy_Makefile
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-xymonproxy_Makefile,v 1.1 2017/09/28 10:40:35 spz Exp $
|
|allow hardening
|
|--- xymonproxy/Makefile.orig 2012-11-14 11:29:54.000000000 +0000
|+++ xymonproxy/Makefile
--------------------------
Patching file xymonproxy/Makefile using Plan A...
Hunk #1 succeeded at 15.
done
/bin/cp /home/pbulk/build/net/xymon/work/xymon-4.3.30/build/Makefile.FreeBSD /home/pbulk/build/net/xymon/work/xymon-4.3.30/build/Makefile.DragonFly
===> Creating toolchain wrappers for xymon-4.3.30nb12
/usr/bin/mkdir -p /home/pbulk/build/net/xymon/work/.buildlink/bin && /usr/bin/ln -fs ../sbin/apxs /home/pbulk/build/net/xymon/work/.buildlink/bin/apxs
/usr/bin/mkdir -p /home/pbulk/build/net/xymon/work/.buildlink/bin && /usr/bin/ln -fs apr-1-config /home/pbulk/build/net/xymon/work/.buildlink/bin/apr-config
/usr/bin/mkdir -p /home/pbulk/build/net/xymon/work/.buildlink/bin && /usr/bin/ln -fs apu-1-config /home/pbulk/build/net/xymon/work/.buildlink/bin/apu-config
===> Configuring for xymon-4.3.30nb12
=> Substituting "bashpath" in xymond/xymonreports.sh.DIST
=> Checking for portability problems in extracted files
Configuration script for Xymon
This script asks a few questions and builds a Makefile to compile Xymon
Checking your make-utility
Checking pre-requisites for building Xymon
Checking for fping ...
OK, will use '/opt/pkg/sbin/fping' for ping tests
Checking for PCRE ...
Compiling with PCRE library works OK
Linking with PCRE library works OK
Checking for C-ARES library ...
Compiling with c-ares library works OK
ld.so.1: test-cares: fatal: libcares.so.2: open failed: No such file or directory
/usr/bin/bash: line 1: 803989 Killed ./test-cares 1.5.1
make: *** [Makefile.test-cares:8: test-link] Error 137
ERROR: Cannot link with c-ares library.
The system C-ARES library is missing or not usable. I will use the version shipped with Xymon
Checking for RRDtool ...
Not RRDtool 1.0.x, checking for 1.2.x
Compiling with RRDtool works OK
Linking with RRDtool works OK
Linking RRD needs extra library: -Wl,-R/opt/pkg/lib -L/opt/pkg/lib -lpng16 -lz -lm
Checking for OpenSSL ...
Compiling with SSL library works OK
Linking with SSL library works OK
Checking if your SSL library has SSLv2 enabled
SSLv2 support disabled (dont worry, all systems should use SSLv1 or TLS)
Checking if your SSL library has SSLv3 enabled
SSLv3 support disabled (dont worry, all systems should use SSLv1 or TLS)
Xymon can use the OpenSSL library to test SSL-enabled services
like https-encrypted websites, POP3S, IMAPS, NNTPS and TELNETS.
If you have the OpenSSL library installed, I recommend that you enable this.
Do you want to be able to test SSL-enabled services (y) ?
Checking for LDAP ...
Compiling with LDAP works OK
LDAP requires the LBER library
Linking with LDAP works OK
ld.so.1: test-ldap: fatal: libldap.so.2: open failed: No such file or directory
/home/pbulk/build/net/xymon/work/xymon-4.3.30/configure.server[158]: .: line 79: 805982: Killed
ld.so.1: test-ldap: fatal: libldap.so.2: open failed: No such file or directory
/home/pbulk/build/net/xymon/work/xymon-4.3.30/configure.server[158]: .: line 80: 805983: Killed
ld.so.1: test-ldap: fatal: libldap.so.2: open failed: No such file or directory
/home/pbulk/build/net/xymon/work/xymon-4.3.30/configure.server[158]: .: line 81: 805984: Killed
Xymon can use your LDAP client library to test LDAP servers.
Do you want to be able to test LDAP servers (y) ?
Checking for clock_gettime() requiring librt ...
Checking for Large File Support ...
Large File Support assumed OK on Solaris
Setting up for a Xymon server
What userid will be running Xymon [xymon] ?
Where do you want the Xymon installation [/opt/pkg/libexec/xymon] ?
OK, will configure to use /opt/pkg/libexec/xymon as the Xymon toplevel directory
What URL will you use for the Xymon webpages [/xymon] ?
Where to put the Xymon CGI scripts [/opt/pkg/libexec/xymon/cgi-bin] ?
(Note: This is the filesystem directory - we will get to the URL shortly)
What is the URL for the Xymon CGI directory [/xymon-cgi] ?
(Note: This is the URL - NOT the filesystem directory)
********************** SECURITY NOTICE ****************************
If your Xymon server is accessible by outsiders, then you should
restrict access to the CGI scripts that handle enable/disable of
hosts, and acknowledging of alerts. The easiest way to do this is
to put these in a separate CGI directory and require a password to
access them.
Even if your Xymon server is on a secured, internal network, you
may want to have some operations (like disabling a host) be password-
protected - that lets you see who disabled or acknowledged an alert.
Where to put the Xymon Administration CGI scripts [/opt/pkg/libexec/xymon/cgi-secure] ?
(Note: This is the filesystem directory - we will get to the URL shortly)
What is the URL for the Xymon Administration CGI directory [/xymon-seccgi] ?
(Note: This is the URL - NOT the filesystem directory)
** Note that you may need to modify your webserver configuration.
** After installing, see /opt/pkg/libexec/xymon/server/etc/xymon-apache.conf for an example configuration.
To generate Xymon availability reports, your webserver
must have write-access to a directory below the Xymon
top-level directory. I can set this up if you tell me
what group-ID your webserver runs with. This is typically
'nobody' or 'apache' or 'www-data'
What group-ID does your webserver use [nobody] ?
Where to put the Xymon logfiles [/var/log/xymon] ?
What is the name of this host [pkgsrc-upstream-trunk] ?
What is the IP-address of this host [127.0.0.1] ?
** NOTE: Using 127.0.0.1 (loopback), but it is probably not what you want **
Where should I install the Xymon man-pages (/usr/local/man) ?
Using SunOS Makefile settings
Created Makefile with the necessary information to build Xymon
Some defaults are used, so do look at the Makefile before continuing.
Configuration complete - now run make (GNU make) to build the tools