[Pythonmac-SIG] wxPython build issue

Bill Northcott w.northcott at unsw.edu.au
Fri Feb 3 08:53:11 CET 2006


On 03/02/2006, at 6:32 PM, Kevin Ollivier wrote:
>> I found that _POSIX_C_SOURCES is defined in pyconfig.h in Python 2.4
>> but not 2.3.  So this problem will only arise using Python 2.4 on
>> Tiger.  Python 2.4 on Panther, or 2.3 on Tiger would be OK.  It seems
>> both Apple and the Python people decided to be IEEE Stds 1003.1-2001
>> compliant, but it has caused a problem in wxWidgets/wxPython.
>
> Thanks for all your help tracking this down! I'm seeing the problem  
> and have made some changes to the wx configure script that fix it  
> on OS X. But I need to check if the fix doesn't break anything on  
> other platforms first. We should have this in the 2.6.3 release  
> (due in a couple weeks), and fixed in HEAD hopefully in the next  
> couple days. (I had been doing my 2.4 builds on Panther, which is  
> why I had not noticed this before!)

Hi Kevin

I thought about this some more and concluded that messing with the  
autoconf stuff might break other extensions that worked now.

After reading more, particularly http://www.opengroup.org/onlinepubs/ 
009695399/functions/xsh_chap02_02.html , I settled on a change in wx/ 
string.h.  It seems to me that if the host is IEEE Std 1003.1-2001  
compliant  then the HAVE_STRCASECMP..... macros should be ignored and  
strings.h included.

So I added more alternative conditions to wx/string.h:46 thus:
#if defined(HAVE_STRCASECMP_IN_STRINGS_H) || _POSIX_C_SOURCE ==  
200112L || _XOPEN_SOURCE == 600

This definitely works on MacOS X 10.4 and I don't see how it can  
break on other systems.

Cheers
Bill Northcott

PS  I still have the issue from my other posting which Adriano posted  
in September.


More information about the Pythonmac-SIG mailing list