On 15-jun-2006, at 9:28, Dan White wrote:
So yes there are some DYLD_LIBRARY_PATH suff set. Maybe therein lies the problem...? Python probably doesn't know about that stuff?
That might be the problem, and seems to indicate that Intel does something completely wrong. Any use of the DYLD_* variables in a production environment is an indication that something fishy is going on. Unlike linux executables on osx contain the full path to libraries they link to. If DYLD_LIBRARY_PATH is needed the compiler doesn't include the full path to some libraries that are needed. It should be possible to teach py2app/macholib about this "feature" of the intel compiler, but you'll probably have to do that yourself.
Ronald
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
