From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Green To: GCC Installation Help List , libstdc++-v3 Development List , Bernhard Rosenkraenzer Subject: Re: Case history: Installing libstdc++ on i686-pc-linux-gnu (Red Hat) Date: Sat, 01 Apr 2000 00:00:00 -0000 Message-ID: <38E2650E.C3548ECF@sputnik7.com> References: <38DFE709.D9B51CBC@sputnik7.com> <38E1B1EA.DCF97B87@sputnik7.com> X-SW-Source: 2000-q1/msg00424.html Message-ID: <20000401000000.J9jfplr8AA5_QaOYDUIGRMOu5knqrgRjBOi-VJiUMjE@z> I wrote: > So: What should I do? Should I look for an old copy of the > libstdc++-libc6.1-1.so.2 file on the 'net and just and paste it back > into /usr/lib? A good deal of the commands on my system require it. > One idea: I observe that the gcc-c++ RPM info says that it "does > include the static standard C++ library and C++ header files; the > library for dynamically linking programs is available separately." > Perhaps that would solve the problem? Or is this something I can > solve by pointing the libstdc++-libc6.1-1.so.2 symlink somewhere > else or by setting LD_LIBRARY_PATH? I found a non-RPM (finally!) copy of libstdc++-libc6.1-1.so.2 in the Slackware distribution. I copied it into /usr/lib, and my commands seem to work fine now. Using ldd(1), I determined that none of the other missing library files are needed by my system except for lib[cm].so.5 and libstdc++.so.27, and although the links with those names were gone, fortunately the underlying files weren't, and I was able to resolve all of the library dependency problems by putting the files and links back into /usr/lib. Hopefully this won't break anything in the new libraries. (Right?) Thanks to everyone for listening. --Avi ========= Avi Green :) (: www.sputnik7.com ========= ======== Unix S/A & System Specialist ======== ======== avi at sputnik7.com 212 217-1147 ========