[MacPorts] #17059: py-setuptools confused about MACOSX_DEPLOYMENT_TARGET
MacPorts
noreply at macports.org
Wed Nov 19 06:25:13 PST 2008
#17059: py-setuptools confused about MACOSX_DEPLOYMENT_TARGET
---------------------------------+------------------------------------------
Reporter: stephen at xemacs.org | Owner: macports-tickets at lists.macosforge.org
Type: defect | Status: new
Priority: Normal | Milestone: Port Bugs
Component: ports | Version: 1.7.0
Resolution: | Keywords:
Port: py-setuptools |
---------------------------------+------------------------------------------
Comment(by stephen at xemacs.org):
OK, the definition from configure stored in .../python2.4/config/Makefile
was MACOSX_DEPLOYMENT_TARGET=10.3. I've just started a "port -f upgrade
python24", and confirmed that in the configure'd Makefile,
MACOSX_DEPLOYMENT_TARGET=10.4.
"To everything (churn, churn, churn) there is a reason (churn, churn,
churn)," and with the musical interlude and the Python upgrade finished,
the value in .../python2.4/config/Makefile now is
MACOSX_DEPLOYMENT_TARGET=10.4, and I've confirmed that py-setuptools (and
bittorrent, which now fails the same way) can be "port upgrade"ed
successfully.
Thank you for your help with this issue!
I can't explain why MACOSX_DEPLOYMENT_TARGET=10.3 was in an installation
less than 5 months old when this system has been running 10.4 for at least
18 months. Maybe it used to be overridden/hardcoded in older versions of
port and/or the Portfile?
--
Ticket URL: <http://trac.macports.org/ticket/17059#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list