(GRRR. System ate my post. "Modify" and "Remove" are vertically next to each other on my browser display, and "Remove" doesn't seem to require a confirmation.)
I am in need of talking with the person responsible for compiling the 2.2.1 release.
I can fix the SDL configuration by copying the section from the 2.3 configure script.
But when I have universal compiling turned on, I get this:
Kleiman-ibook:trunk michael$ make
* [UFO] src/client/cl_actor.c
gcc-4.0: -E, -S, -save-temps and -M options are not allowed with multiple -arch flags
make: *** [debug-darwin-powerpc/client/client/cl_actor.o] Error 1
So how was the 2.2.1 universal compiled?
Second, with universal turned off, I get an error while compiling:
* [UFO] src/ports/unix/unix_main.c
* [UFO] src/ports/macosx/osx_main.m
In file included from /System/Library/Frameworks/Security.framework/Headers/Security.h:24,
from /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Headers/LSSharedFileList.h:32,
from /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Headers/LaunchServices.h:37,
from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:41,
from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20,
from src/ports/macosx/osx_main.m:36:
/System/Library/Frameworks/Security.framework/Headers/cssmconfig.h:64: error: two or more data types in declaration specifiers
/System/Library/Frameworks/Security.framework/Headers/cssmconfig.h:64: error: two or more data types in declaration specifiers
make: *** [debug-darwin-powerpc/client/ports/macosx/osx_main.o] Error 1
I'm trying to tell if this is harmless "code rot", caused by changes in headers from 10.3/10.4 to 10.5. It can be avoided by re-ordering header files. The system file in question is:
51 #ifndef _SINT32
52 typedef int32_t sint32;
53 #define _SINT32
54 #endif
55 #ifndef _SINT16
56 typedef int16_t sint16;
57 #define _SINT16
58 #endif
59 #ifndef _SINT8
60 typedef int8_t sint8;
61 #define _SINT8
62 #endif
63 #ifndef _UINT32
64 typedef uint32_t uint32;
65 #define _UINT32
66 #endif
Since everything seems to be protected by ifdefs, why is causing problems, why is it only showing up here, and does re-ordering the header files to fix this result in unexpected changes elsewhere?
Interestingly, this file has the "strangest" include I've seen yet:
#include <CoreServices/../Frameworks/CarbonCore.framework/Headers/ConditionalMacros.h>
First time I've seen a .. like that in a fixed pathname.