Message113161
I agree that this behavior wrong, this should only trigger an error when building packages.
How did you build python? I guess something like this:
$ export MACOSX_DEPLOYMENT_TARGET=10.5
$ configure --enable-framework
$ make install
This should result in getting the right deployment target into config/Makefile, which means there may be two bugs here:
1) sysconfig.get_config_vars shouldn't trigger and error, only
the distutils build command should do that
2) config/Makefile should always contain the value of MACOSX_DEPLOYMENT_TARGET as used during the build, which in turn should
mean the value during the configure step.
BTW. I tend to configure like this:
$ configure --enable-framework MACOSX_DEPLOYMENT_TARGET=10.5
That way automatic reruns of configure pick up the right environment variables. |
|
Date |
User |
Action |
Args |
2010-08-07 10:10:16 | ronaldoussoren | set | recipients:
+ ronaldoussoren, tarek, srid |
2010-08-07 10:10:15 | ronaldoussoren | set | messageid: <1281175815.96.0.583085021977.issue9516@psf.upfronthosting.co.za> |
2010-08-07 10:10:13 | ronaldoussoren | link | issue9516 messages |
2010-08-07 10:10:12 | ronaldoussoren | create | |
|