Hi Martin, Il 23/07/2011 12:08, Martin Zibricky ha scritto: > Antonio Valentino píše v So 23. 07. 2011 v 11:53 +0200: >> $ which obj >> objcopy objdump >> $ which objdump >> /usr/bin/objdump > > What about > > $ which ldd >
Oh sorry, a wrong paste. Yes ldd is there $ which ldd /usr/bin/ldd >> Anyway, I'm not sure to understand how the #360 (mainly regarding the >> use or relative/absolute paths) can be related to my particular issue. > > Me too, but this is the only recent change made to bootloader code. > > - could you please try comment out the code to set absolute > LD_LIBRARY_PATH and try it again - make sure it is not caused by it? I've just tested it against trunk r1510 ad I get the same error. Now I'm going to test my app packaging with pyinstaller 1.5 (official release). > Another cause could be using gcc 4.5 to compile bootloader. > - I should try an older version > I tested my app with both a bootloader built on my machine (with gcc 4.5.2) the standard bootloader (downloaded from trunk). Which gcc version do you used to build it? >> I'm assuming that libpython *must* be included in the packaged >> application in order to allow the user to run it on a target machine >> that have a different python version installed (or no python at all). >> >> Is it correct? > > Yes, it is correct. > Ok, in this case I will make some test wit a dummy up to be sure it is not my application or my particular spec file setup to mess up. Even if i have to say that the same spec file and the same app work correctly on mac. regards -- Antonio Valentino -- 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.
