Dear List,
here's a quick addition to my previous posting:
GCC, starting with 4.3.0, has reorganised some of its internal overriding
headers. This means that wicked programmes which think they can rely
on GCC's private implementation details remaining unchanged have been
breaking here and there (e.g., glibc up to and including 2.7 won't build
without patching). I suspect you are having the same difficulty.
Here are some details of the glibc problem, in case it helps.
I extracted them from
http://devpit.org/wiki/Gnu_Toolchain/Compatibility_Matrix
Vein: GCC moved limits.h and syslimits.h
GCC: GCC Version 4.3 moved limit.s and syslimits.h to new include-fixed
directory
GLIBC: GLIBC snapshot preceeding Jan 31, 2008 (i.e. GLIBC 2.7)
Description: GCC 4.3 added an include-fixed directory and moved limits.h
and syslimits.h there [3]. Compiling GLIBC 2.7 (or prior) with GCC 4.3
will require these [4] patches to work.
Footnote [3] says
3: From the libc-alpha mailing list:
glibc --with-headers and GCC 4.3ish trunk: include-fixed required
Links to http://www.cygwin.com/ml/libc-alpha/2008-01/msg00067.html
Roland uses a different method (see patch set below).
Links to http://www.cygwin.com/ml/libc-alpha/2008-02/msg00001.html
4: Patches from glibc-cvs mailing list: libc configure.in configure
Links to http://sourceware.org/ml/glibc-cvs/2008-q1/msg00110.html
[This is Roland's patch-set "below", mentioned above]w
I still think you have the wrong thing in /usr/include/limits.h .
Bernard Leak
--
Before they made me, they broke the mould
_________________________________________________________________
Win 100’s of Virgin Experience days with BigSnapSearch.com
http://www.bigsnapsearch.com______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
