Sure, no problem; it will be tonight before I get back to my home workstation though. It's worth a try, definitely. I just always get a queasy feeling when copying executables from one Linux system to another :) (and yes, that does include the output from pyinstaller, py2exe or anything...I did an extensive amount of testing with my app on my "farm" of virtualboxes to make sure that I knew on which systems it worked and did not).
On Tue, Apr 26, 2011 at 11:01 AM, Sloan Lindsey <[email protected]>wrote: > > > On Tue, Apr 26, 2011 at 4:55 PM, dhyams <[email protected]> wrote: > >> To follow up on this too, it might be a better option, in your >> particular situation, to just install Python+numpy+scipy+matplotlib on >> the server, into some area that is writable by you; you should not >> need admin privileges to do so. >> > > No but I have run into problems in the past with ATLAS, I'll try if I'm > totally sunk but past endeavors really make me skeptical. > >> >> It's painful I know, but I don't think there will be any other way to >> run your code on the server that you are wanting to. >> >> Personally, I use Virtualbox, and have a SuSe 11.1 distribution that I >> build my app (via pyinstaller) on. If you have the ability to do >> something similar, that would most likely work for you as well. >> Building in this way gets me an executable that is free from GLIBC ABI >> problems on all current platforms. >> > > I noticed this when I searched from your earlier posts. I then found this > line in 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. > > Is there any chance you would be willing to send me your bootloader > binaries? Or am I completely misparsing that statement? > -Sloan > >> >> -- >> 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. >> >> > -- > 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. > -- Daniel Hyams [email protected] -- 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.
