Realplay broken?

Patrick O'Callaghan pocallaghan at gmail.com
Thu May 22 11:07:01 UTC 2008


On Thu, 2008-05-22 at 10:51 +0200, xkey wrote:
> i have a really stupid question here since i hadnt used linux in 10 years but after just dealing with Fedora 9 and some apps that wanted  libstdc++.so.5   
> i came across this and another useful link
> i got the rpm and had to force it using the following
> rpm -ivh --force compat-libstdc++-33-3.2.3-63.x86_64.rpm

Why did you have to force it? It installed for me without forcing.

> then i checked with
> rpm -qi compat-libstdc++-33
> and it came back with appropriate info
> 
> and my app ran
> 
> BUT my question is - where did it install libstdc++.so.5?? locate and some other commands fail to find it in any dir

rpm -ql compat-libstdc++-33|grep libstdc++.so.5

On my system it's in /usr/lib and /usr/lib64.

> actually then i have more questions
> in the future how can i force a directory??? - i really want that lib in  usr/lib    but the only useful info i found in rpm help was about old file path and new file path 
> but a lot of time i just want one lib out of some repository

Install it and then move it or use a symlink, but don't expect it to
work. If the package wants it in a specific place it's usually for a
good reason. Package installation doesn't just plonk a file somewhere,
it runs scripts and updates a database. Moving stuff around (even if it
works) is likely to screw up any future updates, so you're losing most
of the advantages of using a package system in the first place.

poc




More information about the test mailing list