On Monday 08 Feb 2010, Mats Bertil Tegner wrote: > On 02/08/2010 08:01 PM, leee wrote: > > On Monday 08 Feb 2010, Mats Bertil Tegner wrote: > >> On 02/08/2010 07:31 PM, leee wrote: > >>> The only way of guaranteeing the full functionality is to > >>> install the required library. If you don't need the AVI > >>> functionality then you can ignore the messages. > >>> > >>> You could try setting up a symlink from your libavcodec.so.52 > >>> to libavcodec.so.51 but if the library entry points have > >>> changed between those two versions then you'll likely just > >>> get a different error message and still won't have the > >>> functionality. > >>> > >>> LeeE > >> > >> I tried changing the symlink, but I'm unable to make a third > >> symlink to libavcodec.so.52.36.0, so I will ignore the AVI > >> functionality for now. > >> > >> Mats > > > > Do not try to change any existing symlinks because that will > > most likely stop other stuff from working. > > > > Why could you not create a new symlink? Did you try to do so > > as a normal user? As it's a system directory you'd need to be > > a superuser, or use sudo to write the new symlink to it. > > > > LeeE > > I was superuser when I tried to make the symlink. Here is the > output: bash-3.1# ln -s libavcodec.so.51 libavcodec.so.52.36.0 > ln: creating symbolic link `libavcodec.so.52.36.0': File exists > > What am I missing? > Mats
You've specified the target and link names in the wrong order. Instead of "ln -s libavcodec.so.51 libavcodec.so.52.36.0" you should have used "ln -s libavcodec.so.52[.36.0] libavcodec.so.51" Usage: ln [OPTION]... [-T] TARGET LINK_NAME LeeE
