On 02/11/15 19:40, Michael Felt wrote:
Yes, xlC, and I was hoping it was just a stray gcc flag.
If that's indeed the reason, you can:
(0) To confirm whether it is, replace WERROR_CFLAGS="-Werror" with
WERROR_CFLAGS="" in configure.ac, run autoconf, configure etc.
If that works:
(1) find an equivalent flag for XL C and create a patch, just like the
one for SunPRO [1]. If I understand the documentation right [2], this
could be "-qmaxerr=1:w" (increase the number 1 if some 'statement not
reached' stuff gets in your way), but it's difficult to say without an
actual installation to test.
(2) create a patch similar to (1), but set WERROR_CFLAGS="" or disable
the scandir check altogether when compiling with XL C. I believe before
[3] there wasn't even a scandir check, and the change was only to
silence warnings on NetBSD if I read the commit right. I doubt you will
have any problem on AIX.
Actually I'm still somewhat unhappy that configure wants to acknowledge
the POSIX version of scandir specially when only recognizing the NetBSD
version would probably have sufficed ... would have saved us a lot of
if's, maybe even the one for $os_win32.
But I'll shut my mouth again.
-Raimund
[1]
http://cgit.freedesktop.org/fontconfig/commit/?id=694368667a15341ea30b37a36e9540e6b1492680
[2]
http://www-01.ibm.com/support/knowledgecenter/SSGH2K_13.1.0/com.ibm.xlc131.aix.doc/compiler_ref/opt_maxerr.html?lang=en
[3]
http://cgit.freedesktop.org/fontconfig/commit/?id=38ab7ab2fbd83c0c62e4b78302b5fe89da0cb79e
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig
