Sebastian Hilbert wrote: > On another system it complain about missing libraries such as > libpython2.4.so depsite the fact that the *.so file *is* right there, > included in the same directory as the built gnumed executable. > > What do I miss here ? > > built on SUSE 10.1 > tested on same system --> works fine > tested on Debian Sarge --> missing library > > Ok I went ahead and added the distgnumed directory to the LD-PATH and > now it complains of somethinh different : > > ./gnumed: relocation error: ./gnumed: symbol __strcpy_chk, version > GLIBC_2.3.4 not defined in file libcso.6 with link time reference > > Any help is appreciated
The problem appears to be that GLIBC is only *forward* compatible. If you link an application against version X of GLIBC, you can run it only on systems with GLIBC > X. So, ideally, you should compile and link the bootloader against the oldest version of GLIBC you want to support, so that it will work on any newer system. In your case, you could compile the bootloader of PyInstaller in the Debian Sarge system, and then copy the bootloader binaries over to the SUSE system (if that's your development computer). This should fix the problem. I await a confirmation :) Giovanni Bajo _______________________________________________ PyInstaller mailing list [email protected] http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
