From owner-freebsd-bugs Tue Nov 13 12:50: 5 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 314D537B405 for ; Tue, 13 Nov 2001 12:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id fADKo2x99390; Tue, 13 Nov 2001 12:50:02 -0800 (PST) (envelope-from gnats) Date: Tue, 13 Nov 2001 12:50:02 -0800 (PST) Message-Id: <200111132050.fADKo2x99390@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: misc/31955: ULONG_MAX defined as hex on freebsd, ULONG_MAX defined as int on GNU, breaks autoconf Reply-To: David Malone Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR misc/31955; it has been noted by GNATS. From: David Malone To: Sean Jensen-Grey Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/31955: ULONG_MAX defined as hex on freebsd, ULONG_MAX defined as int on GNU, breaks autoconf Date: Tue, 13 Nov 2001 20:49:05 +0000 On Tue, Nov 13, 2001 at 12:23:28PM -0800, Sean Jensen-Grey wrote: > Now my question is. Is this actually a bug? This is a bug in either boa configure script or autoconf, I guess. It's reading a C header file, so it should be expected to understand anything which C can. I'll close the PR, unless you feel strongly otherwise? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message