On Jun 12, 2005, at 9:03 AM, Jeremy Higgs wrote:
error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.4" but "10.3" during configuremake[1]: *** [neo_cgi.so] Error 1The compile continues, but the file (neo_cgi.so) is not compiled, and therefore not installed... which is a bit of a problem.Does anyone know how to fix this? The MACOSX_DEPLOYMENT_TARGET variable is not set anywhere in the package by me, so I don't know what's causing it to think that it was set to 10.3 earlier...
This problem seems to happen because the python2* packages write the current MACOSX_DEPLOYMENT_TARGET to %p/lib/python2.3/config/Makefile and the python build utilities use this value when compiling modules. This means that if you have a python24 from 10.3 (from the bindist or by upgrading 10.3 => 10.4), there will be a mismatch between what python thinks MACOSX_DEPLOYMENT_TARGET should be and what it actually is.
The immediate fix is to 'fink rebuild python24'. So that users don't encounter this bug, it might be smart to bump the revision for python2* on Tiger to force rebuilds.
Dave
PGP.sig
Description: This is a digitally signed message part