On 4/2/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > > > This is the problem. The relative link "libGL.so.1 -> libGL.so.1.2" > shouldn't exist in /lib. Could you try to run DisableProgram on both Mesa > and Nvidia and make sure that you have no libGL.so links in /lib? Then try > to resymlink them again. > > > While in /Programs/NVidia/Current/lib I have: > > > > libGL.so -> libGL.so.1 > > libGL.so.1 -> libGL.so.1.0.9746 > > libGL.so.1.0.9746 > > > > So, it seems SymlinkProgram doesn't handle symlinking symlinks correctly? > > > It doesn't handle relative symlinks in the /System/Links directory. I have > tried to reproduce this bug forcing conflicts in all ways I can think of > and having relative symlinks in the /System/Links directory produced this > exact problem. >
I think I had the same problem upgrading Mesa 6.5 -> 6.5.1. I couldn't get direct rendering enabled. Finally I just removed 6.5 and all my problems disappeared. So why does Mesa 6.5 have this problem? Is it tied to 013 only or the package in general? Any other packages with similar problems. Should SymlinkProgram be altered to handle this? PS I'm adding gobolinux-devel because this may be a SymlinkProgram issue. -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
