Hello misi, The best protection against .so dependency failures is to avoid it alltogether by compiling to a static version of the libraries.
Similarly, did you consider to copy a version of your libc .so's to (and possibly other dependency libraries) the hosting machine and use LD_LIBRARY_PATH to ensure that you're using the intended versions? I haven't really thought this through, I may have overlooked unpleasant side effects... Regards, Wim. 2009/2/1 misi e <[email protected]>: > Hello, > > I am building on a ubuntu 8.10, and trying to run on a webhosters server > thar has debian etch. and get the errors. (latest debian has only GLIBC 2.3, > and I cannot compile there...) > > GLIBC_2.7' not found required by libhttp.so, GLIBC_2.4' not found, required > by libWt.so > > > I got a hint to compile with -fno-stack-protector to avoid dependency on > GLIBC_2.4, but does not work. > > > > any suggestions for compiler flags, to avoid dependency on GLIBC higher than > 2.3? > > > > Regards > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > witty-interest mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/witty-interest > > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
