Re: [AD] allegro-config not working under macosx

[Grzegorz Adam Hankiewicz <gradha@xxxxxxxxxx>]

On 2007-05-27, Peter Wang <novalazy@xxxxxxxxxx> wrote:
> How's this?

That's nice. Next is a problem compiling the alpy extension. Looks like
the 'static auto config' defines in alosxcfg.h are conflicting with
those in Python 2.5 headers (error attached).

I undefined manually HAVE_DIRENT_H, HAVE_INTTYPES_H, HAVE_STDINT_H,
HAVE_SYS_TIME_H, TIME_WITH_SYS_TIME and HAVE_SYS_STAT_H to make it
compile.

I don't remember having this issue with a previous version of Python
months ago on a mac, so I don't know if this was introduced by Allegro
or Python. To me it looks 'uneducated' to publish these generic autoconf
defines in a header visible by end user code, begs for conflicts. OTOH
at my previous job we just ignored such warnings hapilly.

building '_alpy' extension
creating build/temp.macosx-10.3-fat-2.5
gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -I/usr/local/include -I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c _alpymodule.c -o build/temp.macosx-10.3-fat-2.5/_alpymodule.o -Wno-deprecated-declarations
In file included from /usr/local/include/allegro/internal/alconfig.h:54,
                 from /usr/local/include/allegro/base.h:40,
                 from /usr/local/include/allegro.h:25,
                 from src/_alpymodule.c.in:29:
/usr/local/include/allegro/platform/alosxcfg.h:35:1: warning: "HAVE_DIRENT_H" redefined
In file included from /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Python.h:8,
                 from src/_alpymodule.c.in:28:
/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pyconfig.h:112:1: warning: this is the location of the previous definition