Date: Sun, 21 May 2006 02:11:31 +0930 From: Jarrod Sayers <jarrod@netleader.com.au> To: Sam Lawrance <lawrance@FreeBSD.org>, freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/97328: [maintainer-update] net-mgmt/nagios: Update to Nagios 2.3.1 Message-ID: <90AD2202-B3C9-47EE-AEC7-3BD04B258F71@netleader.com.au> In-Reply-To: <200605180816.k4I8GK0p064399@freefall.freebsd.org> References: <200605180816.k4I8GK0p064399@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sam,
I believe I have located the problem. The declaration of INT_MAX
appears in limits.h which is not directly included anywhere in the
distribution, though is tested by the configure script. From what I
can see, limits.h has worked its way in from the inclusion of
pthread.h inside ${WRKSRC}/include/config.h.in on earlier FreeBSD
releases (this build of Nagios is the first to use INT_MAX).
The pthread.h found on -CURRENT installations does not include this,
but includes machine/_limits.h instead which, following those
#includes, doesn't end up with a declaration for INT_MAX.
I have updated the diff (use URL below) to include a patch to add a
manual (and hopefully temporary) #include <limits.h> where needed to
replicate previous behavior:
http://www.netleader.com.au/~jarrod/FreeBSD/net-mgmt-nagios-2.3.1-
pthread.diff
Files Modified:
- ports/net-mgmt/nagios/Makefile
- ports/net-mgmt/nagios/distinfo
Files Added:
- ports/net-mgmt/nagios/files/patch-cgi__getcgi.c
Thanks for spotting that, I have since added a -CURRENT machine into
our build pool.
Jarrod.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90AD2202-B3C9-47EE-AEC7-3BD04B258F71>