David Stern <[EMAIL PROTECTED]> writes: > On 27 Mar 1999 23:14:05 +0200, wrote: > > I hope noone minds if I expand on this thread a little. Sorry, but > there's too much to quote. Summary: running up to date potato, > apparently glibc2.1 replaced glibc2.0 and staroffice stopped working. > > Jules Bean suggested a wrapper for staroffice: > 1.) Get ldso from slink > 2.) mkdir /usr/local/glibc2.0 > 3.) dpkg-deb -x ldso_1.9.10-1.deb /usr/local/glibc2.0 > > The original suggestion which did not work for me was to append .real > to the binary and to chmod +x a wrapper script (all on two lines). > #!/bin/sh > LD_LIBRARY_PATH=/usr/local/glibc2.0/lib:$LD_LIBRARY_PATH > /usr/local/glibc2.0/lib/ld-linux.so.1.9.10 soffice.bin.real > > However the staroffice binary already has a wrapper (soffice calls > soffice.bin), and it looks like it might be better to add the needed > code there rather than an additional layer of encapsulation. Since > soffice (wrapper) has > LD_LIBRARY_PATH=$sd_inst/lib:$LD_LIBRARY_PATH > export LD_LIBRARY_PATH > > I should be able to add my glibc2.0 path: > # set the glibc2.0 path > glibc2.0_path=`/usr/local/glibc2.0/lib` > export glibc2.0_path > > LD_LIBRARY_PATH=$glibc2.0_path:$sd_inst/lib:$LD_LIBRARY_PATH > export LD_LIBRARY_PATH > > Now all that's left is to somehow tell the staroffice binary to use the > ldso from glibc2.0. Originally, soffice calls the binary: > exec $sd_inst/bin/$sd_binary "$1" "$2" "$3" "$4" "$5" "$6" "$7" > "$8" "$9" > I've tried a number of ways that don't work, but is there a good way to > inform soffice.bin to use /usr/local/glibc2.0/lib/ld-linux.so.1.9.10? > (I've checked for dependent packages, bugs, changelogs.) > > Would someone please confirm that ld-linux.so.1.9.10 is the correct > ldso? My potato system is showing a ld-linux.so.2 as linking to > ld-2.1.1.so, which to me infers I might not have the correct ldso > package to run staroffice5 (because ld-linux.so.1.9.10 might not be > glibc2.0).
Hey David ! I did that patch to my StarOffice and it starts again under Potato, but it doesn't print anymore !!! Have you also a soultion for this problem ??? CU Frank
