[gobolinux-users] Trying to install nVIDIA - script may need update

[Jonas Karlsson]

On Mon, 02 Apr 2007 13:32:15 +0200, Jonatan Liljedahl <lijon at kymatica.com>  
wrote:

> Nick Matteo wrote:
>> On 3/31/07, teique <teique at gmail.com> wrote:
>>> !! /lib/libGL.so.1 -> libGL.so.1.5.060500
>>> *mmm*, the beggining of my Konsole history is lost by now :/
>>> as I remember, I did
>>> $ link -sf libGL.so.1.0.9755 /lib/libGL.so.1
>>> so it was towards nvidia,
>>> and then, by curiosity and to let ldconfig happen thru SymlinkProgram,
>>> I run
>>> $ SymlinkProgram nvidia
>>> and it symlinked back again to mesa one...
>>> $ /lib/libGL.so.1 -> libGL.so.1.5.060500
>>> (offtopic: I wonder if there is a way to default Konsole to unlimited
>>> history on new sessions...)
>>
>> There certainly is, just set the history to unlimited, then choose
>> "settings->save as default"
>>
>> SymlinkProgram nvidia shouldn't point anything towards mesa, unless
>> the libGL.so.1 in the nvidia directory is pointing at
>> libGL.so.1.5.060500?
>
> I think there's some problem with symlinkprogram... I have the same
> problem here, and though symlinking NVidia with -c overwrite says:
>
>   SymlinkProgram: Conflict: /Programs/Mesa/6.5/lib/libGL.so.1.2
>   SymlinkProgram: Replaced with:
> /Programs/Nvidia/x86-1.0-9746-pkg1/lib/libGL.so.1.0.9746
>
> I still have in /lib:
>
> libGL.so.1 -> libGL.so.1.2
> libGL.so.1.2 -> /Programs/Mesa/6.5/lib/libGL.so.1.2
>
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.

-- 
/Jonas

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/