Ned Deily <n...@acm.org> added the comment:
I can reproduce this. Chances are you'll see that the python.exe has been
dynamically linked to the MacPorts Python instead of the just produced
libpython2.7.dylib :
$ otool -L ./python.exe
./python.exe:
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/Python
(compatibility version 2.7.0, current version 2.7.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.1.5)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
(compatibility version 150.0.0, current version 476.19.0)
/usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version
47.1.0)
No doubt you can work around it by removing the --enable-shared and/or removing
the MacPorts Python2.7 from the picture. It's not yet clear to me why it's
getting linked that way (--enable-shared on OS X doesn't get tested all that
much as we normally do framework builds) but I'm very doubtful it has anything
directly to do with hg vs svn checkout.
----------
assignee: -> ned.deily
components: +Build
versions: +Python 2.7
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue11445>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
