Thanks for the hint. This helped us a lot, but we don't quite have the
complete answer.
We were never linking to Python 2.3, but otool shows us that we have
references to /Library/Frameworks/Python.framework in our extensions
(and in the embedded Python executable) rather than to
@executable_path/../Frameworks/Python.framework.
If we manually change all these references using:
install_name_tool -change \
/Library/Frameworks/Python.framework/Versions/2.4/Python \
@executable_path/../Frameworks/Python.framework/Versions/2.4/Python \
myfilename.so
the program works.
So now the question is how do we convince py2app to do this for us?
I'm guessing it may have something to do with the way we build our
extensions, but I can't figure out how to convince XCode to brand them
properly.
Kent
-----Original Message-----
From: Bob Ippolito [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 26, 2005 1:33 AM
To: Kent Quirk
Cc: pythonmac-sig@python.org
Subject: Re: [Pythonmac-SIG] Upgraded to 2.4 and can't make it work
You definitely have something that's linking to Python 2.3. Try
DYLD_PRINT_LIBRARIES and/or run it under gdb and backtrace to see
which init function is failing.
<snip>
otool -L on any extension file will tell you what it's linked to..
py2app ships with a tool called macho_find which will find all of the
Mach-O files in a folder... uh, here's a script that should help you
find the culprit:
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
