Follow-up Comment #5, bug #18961 (project gnustep):
I found the error. GCC 4.3.0 brings its own limits.h which defines
LONG_LONG_MAX. Says cpp43 on my system when I paste the test code from
configure and add "LONG_LONG_MAX" and "LLONG_MAX":
#ifndef _GNU_SOURCE
#define _GNU_SOURCE
#endif
#ifdef HAVE_STDINT_H
#include <stdint.h>
#endif
#include <limits.h>
#if defined(LONG_LONG_MAX)
#if LONG_MAX == LONG_LONG_MAX
#error long max equals long long max
#endif
#else
#error long long max not defined
#endif
LONG_LONG_MAX
LLONG_MAX
^D
[snip]
# 1 "/usr/include/sys/syslimits.h" 1 3 4
# 132 "/usr/include/limits.h" 2 3 4
# 123
"/usr/local/lib/gcc-4.3.0/gcc/i386-portbld-freebsd6.1/4.3.0/include/limits.h"
2 3 4
# 8
"/usr/local/lib/gcc-4.3.0/gcc/i386-portbld-freebsd6.1/4.3.0/include/syslimits.h"
2 3 4
# 12
"/usr/local/lib/gcc-4.3.0/gcc/i386-portbld-freebsd6.1/4.3.0/include/limits.h"
2 3 4
# 8 "<stdin>" 2
# 16 "<stdin>"
9223372036854775807LL
0x7fffffffffffffffLL
So they are both defined and both aliases for one and the same number. Now,
"./configure CC=gcc43 CPP=cpp43" tests things under gcc43 conditions but
doesn't actually set the compiler to gcc43 when gmaking, I have to explicitly
say "gmake CC=gcc43". Duh! I should have noticed this earlier.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?18961>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
