[issue11808] $MACOSX_DEPLOYMENT_TARGET mismatch ... during configure

Steffen Daode Nurpmeso added the comment: On Sat, Apr 09, 2011 at 03:58:11PM +, Ned Deily wrote: > By the way, since you've asked about it before, > MACOSX_DEPLOYMENT_TARGET is a standard feature of the Apple gcc > tool chain and is used to support builds for multiple versions. > See -mm

[issue11808] $MACOSX_DEPLOYMENT_TARGET mismatch ... during configure

Ned Deily added the comment: Thanks for the report. This is another case of the problem described in Issue9516, in particular msg130666 except now it is hg invoking another Python during the build process. The sysconfig part of the patch for Issue9516 applied to the "build" Python 2.7 used

[issue11808] $MACOSX_DEPLOYMENT_TARGET mismatch ... during configure

Steffen Daode Nurpmeso added the comment: The problem goes away if i comment out all the Mercurial queries in Makefile: HGVERSION= #hg id -i $(srcdir) HGTAG= #hg id -t $(srcdir) HGBRANCH= #hg id -b $(srcdir) -- ___ Python tracke

[issue11808] $MACOSX_DEPLOYMENT_TARGET mismatch ... during configure

Steffen Daode Nurpmeso added the comment: P.S.: this does not happen if i use ./configure --prefix="$HOME/usr/opt/$PREFIX" $DEBUG MACOSX_DEPLOYMENT_TARGET=10.6 -- ___ Python tracker

[issue11808] $MACOSX_DEPLOYMENT_TARGET mismatch ... during configure

New submission from Steffen Daode Nurpmeso : Hello Mac OS X gurus, if i else DEBUG='--with-pydebug' echo Using --with-pydebug fi ./configure --prefix="$HOME/usr/opt/$PREFIX" $DEBUG make -j2 all i get this /usr/bin/gcc -c -fno-strict-aliasing -g -O0 -Wall -Wstrict-prototypes