|
From: | Richard Frith-Macdonald |
Subject: | [bug #18961] configure enables both HANDLE_LLONG_MAX and HANDLE_LONG_LONG_MAX, resulting in a build error in GSFormat.m on FBSD 6.2 |
Date: | Mon, 05 Feb 2007 12:59:34 +0000 |
User-agent: | Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en) AppleWebKit/418.9.1 (KHTML, like Gecko) Safari/419.3 |
Follow-up Comment #2, bug #18961 (project gnustep): I don't quite understand this report. You say that only LLONG_MAX is defined, in which case line 113 should evaluate to true, but you say it evaluates to false. Did you mean to say that on FreeBSD 6.2 both LLONG_MAX and LONG_LONG_MAX are defined? If so, why does line 123 evaluate to true? the !defined(LONG_LONG_MAX) should evaluate to false. if not, why does line 123 evaluate to true? the defined(HANDLE_LONG_LONG_MAX) should evaluate to false. Could something have changed on your system between configuring and compiling, such that the HANDLE_... value set by the configure script don't match the preprocessor constants set in limits.h? Or could it be that your system supports both forms but switches between them depending on what headers are includes and what preprocessor constants are defined before the headers? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?18961> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |