Jonas Walld?n @ Pike developers forum wrote:
Therefore I disabled the MACOSX_DEPLOYMENT_TARGET=10.3 macro. Not sure what negative impact this has. People with MacOSX experience, please look into it (I merely tested it on my Leopard MacBook).
We're still building on 10.4 and 10.5 in various combinations of PPC32, x86 and x86_64 and I'd be concerned this change leads to
# 10.3 or newer take advantage of two-level namespaces to avoid # symbol collisions for e.g. libjpeg which is referenced from both # _Image_JPEG and _Image_TIFF. It requires MACOSX_DEPLOYMENT_TARGET # which is initialized in smartlink to 10.3. LDSHARED="$REALCC $CFLAGS -bundle -bind_at_load -undefined dynamic_lookup"
Have you checked whether those modules still work? Any change if you
Sorry, no. I'm not using the MacBook for anything other than a movable terminal. I just installed a minimal Pike tree to zoom in on the testsuite problems.
assign a more recent version number to the environment variable? I don't see a problem with discontinuing support for 10.3 specifically if that helps.
Well, on my Leopard MacBook, setting it to 10.4 exhibits the same problem, setting it to 10.5 solves it. Basically, this is only relevant during the compilation of file.c. So if the compilation of this file could be singled out, it might be solved as well.