yes, I was also thinking fun huh! my server, actually the nas giving the iscsi, crashed, so I have a bit of rebuilding to do. <div class="gmail_quote">On Mar 2, 2015 6:37 PM, "Michael Haubenwallner" <<a href="mailto:michael.haubenwallner@ssi-schaefer.com">michael.haubenwallner@ssi-schaefer.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 02/15/2015 09:34 PM, Michael Felt wrote: > "/usr/include/unistd.h", line 171.17: 1506-343 (S) Redeclaration of lseek64 differs from previous declaration on line 169 of "/usr/include/unistd.h". > "/usr/include/unistd.h", line 171.17: 1506-050 (I) Return type "long long" in redeclaration is not compatible with the previous return type "long". <snip> > So, it seems there is an inaccurate assumption regarding the affect/interaction of _LARGE_FILES and _LARGE_FILE_API > > Looking at <a href="http://config.h.in" target="_blank">config.h.in</a> <<a href="http://config.h.in" target="_blank">http://config.h.in</a>> - it looks as it _LARGE_FILES was added to assist with AIX, and now it is getting the way (fun :p) > > I cannot find where the code for configure is generated. I suspect that - MAYBE - this was important for when > 32-bit hardware was out there (in 1997 64-bit file support was added to AIX 4.2.0 even though the kernel was > still 32-bit as well as 'normal' pointers. > > In any case - this was not a problem I encounter with fontconfig-2.4.2 (ancient!!) but do now. > > Give me hints, and I shall test them (as I have time). This should be fixed along <a href="https://bugs.freedesktop.org/show_bug.cgi?id=89336" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=89336</a> now. /haubi/ </blockquote></div>