Jim Perrin wrote: > On 12/10/05, Alex White <ethericalzen at gmail.com> wrote: > >>Jim Perrin wrote: >> >>>On 12/10/05, Preston Crawford <me at prestoncrawford.com> wrote: >>> >>> >>>>On Sat, 2005-12-10 at 11:46 -0600, Alex White wrote: >>>> >>>> >>>>>Well libstdc++ exists in /usr/lib/ on my system 4 U2 it's: >>>> >>>>Okay, I wasn't sure which one I'd symlink off of. I appreciate the >>>>explanation. >>>> >>>> >>>> >>>>>Now, if you know that your application is erroring off with >>>>>something similar to "unable to locate libstdc++.so.2" Just as an >>>>>example, then you could do something like: ln -s >>>>>/usr/lib/libstdc++.so.5 /usr/lib/libstdc.so.2 >>>> >>>>I need to look at the error log. It might be looking in an entirely >>>>different location, maybe? I mean either it's hard-coded to look for a >>>>certain version or to look somewhere else (assuming it's possible that >>>>RHEL 2.x ut libstdc somewhere else). >>>> >>>> >>>> >>>>>If that doesn't work then just delete your symlink and all will be >>>>>right with the world. Make sure not to delete the actual library >>>>>though, I've done somethin' stupid like that before lol >>>> >>>>:-) >>>> >>>>Thanks. >>>> >>> >>>Instead of wrecking systems with random symlinks trying to meet >>>compatible versions of things, why not do "yum provides filename" and >>>see if it is available to you. >>> >>>yum list "compat*" yeilds several packages that might be what you're >>>looking for. >> >>Thank you for clearing that little bit up. Because you know..I've >>destroyed numerous machines in my career over a single app. *blinkles* >> >>Alex White > > > > eh. I hadn't planned on starting up another mailing list pissing match > here, nor do I feel like engaging in one. Ask any 8 administrators how > to do something and you'll get 9 ways to do it. Yes, your way may > well work, and you may be happy with that. But what happens down the > road for the next app and the app after that? Instead of symlinking > newer libs to older lib names, why not simply see if you have the > older lib available to you? That was my whole point. What happens when > you create this type of symlink to a file you later install via yum? > Even if you're aware of little tweaks like this and they work but > they're not the absolute pristine ivory tower elitist way to solve > things, it's possible the person asking on the list may not know any > better, and for subsequent apps may get link happy. > > Yes. Your way works and probably well, but it's not ivory tower > quality advice for people still learning. I teach best practice type > things on a daily basis, and I make every effort to carry that into > what I post for help on the list. > > /last comment > //will not continue this thread > ///implore others not to let this thread grow to the absurd lengths of others. > Discussed off list and resolved. Excuse the waste of bandwidth. Alex White