Colin Watson <[EMAIL PROTECTED]> writes: > On Tue, Dec 10, 2002 at 11:28:19AM -0500, Dragan Cvetkovic wrote: > > Does this one gives you a clue? Your system can't find > > libstdc++-libc6.1-1.so.2 > > > > What I did on my system was to create a symlink from whatever current > > libstdc++-libc6 so library in /usr/lib is to > > $HOME/lib/libstdc++-libc6.1-1.so.2 and add $HOME/lib to my LD_LIBRARY_PATH > > env. variable. > > > > Not really a solution in a Debian way(tm), but works. > > Rodrigo has the right answer here. It's not so much that your solution > isn't the "Debian way", it's that it's potentially unreliable. The > soname of a library changes because something changed in the library to > render it incompatible with previous versions; it might not be anything > you'll notice right away, but it's better to avoid the chance that > something will inexplicably fall over three months from now when you've > forgotten what you did.
You are right Colin. The most ironic thing is that I _did_ have libstdc++2.9-glibc2.1 installed so my symlink wasn't needed at all. I have removed it now. The only one remaining there is libreadline.so.3, which points to /usr/lib/libreadline.so.4, since I couldn't find it anywhere on Debian. Of course, I can't remember why did I need it :-( I guess I can remove the link and see what breaks :-) Bye, Dragan -- Dragan Cvetkovic, To be or not to be is true. G. Boole No it isn't. L. E. J. Brouwer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
