King píše v Út 16. 02. 2010 v 10:07 -0800: > > Here are the details of my hardware and software used in tests: > #---- System Information ----# > GUI2Exe Version: 0.5.0 > Operating System: Linux 2.6.31-14-generic i686 > Python Version: 2.6.4rc2 (r264rc2:75497, Oct 20 2009, 02:55:11) > [GCC 4.4.1] > wxPython Version: 2.8.10.1 (gtk2-unicode) > wxPython Info: (__WXGTK__, wxGTK, unicode, gtk2, wx-assertions-off, > SWIG-1.3.29) > Python Encoding: Default=UTF-8 File=UTF-8 > wxPython Encoding: utf-8 > System Architecture: 32bit i686 > Byte order: little > Frozen: False > #---- End System Information ----# > >
All of your questions are somehow related to the pyinstaller's bootloader and gcc/glibc version what is used to compile bootloader. Info from the FAQ: - Under Linux, I get runtime dynamic linker errors, related to libc. What should I do? The executable that PyInstaller builds is not fully static, in that it still depends on the system libc. Under Linux, the ABI of GLIBC is backward compatible, but not forward compatible. So if you link against a newer GLIBC, you can't run the resulting executable on an older system. The solution is to compile the bootloader on the oldest system you have around, so that it gets linked with the oldest version of GLIBC. Then, you can copy the bootloader binaries (support/loader/*) into your development system and run Build.py there. See also this ticket: http://www.pyinstaller.org/ticket/145 > 1. Are there any issues when running the deployment on other distros > like fedora or open suse? it is related to the glibc version and what versions of glibc do those distros use. > > 2. Are there any issues when running the deployment on 64 bit machine > where as the application has been created on 32 bit architecture? I think on 64-bit you'll need to install 32 bit libraries in order to run it. Don't know if any 64-bit distros, when installed, contain already some 32-bit libs. > > 3. What if user try to run the app on the same distro but either a > newer or an older version? Newer versions should work, older not. > > 4. The deployed package should be be self sufficient but still I am > sure it would be having some external dependencies.(libc*.* or what > ever) If yes, what are those dependencies that user must take care > of? Package will always depend on glibc. I think it should be the only dependecy. But I think it depends on libraries what you use and how are implemented pyinstaller hooks for freezing various python libraries. -- 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.
