On 5/20/2009 8:54 AM, [email protected] wrote: >> Bad news. I just installed CentOS 5.3 and I'm getting the exact same >> problem, so there's definitely something wrong... (same no parsers >> found problem). Sigh. >> > > This is still a mystery to me. I found a bit more info, but it's > really hard to pin down what's actually going on.
Can I get SSH access to the build OpenSUSE and CentOS systems? I would love to debug this problem. > 1/ OpenSUSE 10.2 has python2.5 installed; CentOS has python2.4 > installed. On OpenSUSE I can do aggressive things like renaming /usr/ > lib/python2.5 and /usr/local/lib/python2.5 to some dummy directory and > still run the application fine. > > 2/ using strace shows some strange differences. E.g on OpenSUSE the > libssl*so library is loaded from /usr/lib/; on CentOS that library is > not installed in the system path, but it is bundled with the > application. However, the strace shows that it does _not_ try to load > libssl from the current directory. > > 3/ doing something aggressive like linking /usr/lib/python2.5 to /usr/ > lib/python2.4 on CentOS causes the application to segfault. In this specific scenario (segfault), can you try again after reverting commit [652] in PyInstaller and building a new executable? > This > surprised me, because the application is supposed to be selfcontained, > no? Why is it looking at /usr/lib/python* in the first place ? (not > that I expected this hack to actually work -- I just wanted to see if > it would try to access python2.5 in some way). Py_Initialize() imports the "encodings" package before anything can be done to prevent it. The prefix path (/usr/lib/python) is hardcoded within python itself. This happens only under Linux. I can't see any way of preventing it short of patching the libpython.so to remove the hardcoded prefix from it. I'll of course open a bugreport to Python developers but I don't have any hopes. > This seems to indicate some problem with the load path. Could that be > the problem? > > Kindof at a loss here... anybody any thoughts on what I can try next ? Can you try with this program: ========================================== import xml print xml.__version__ import xml.sax print xml.sax.saxexts.__file__ print xml.sax.make_parser() ========================================== This should give us some hints at what it is going on. -- Giovanni Bajo Develer S.r.l. http://www.develer.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en -~----------~----~----~----~------~----~------~--~---
