Bug#773303: libgl1-mesa-dev: Symlink error for libGL.so

[Shan Ting <shantingst@gmail.com>]

Hello Simon,

In my system,

sudo stat /usr/lib/x86_64-linux-gnu/libGL.so
  File: ‘/usr/lib/x86_64-linux-gnu/libGL.so’ -> ‘libGL.so.1.2.0’
  Size: 14        	Blocks: 0          IO Block: 4096   symbolic link
Device: 802h/2050d	Inode: 3834685     Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2014-12-17 14:39:23.341047921 +0800
Modify: 2014-10-27 19:44:20.000000000 +0800
Change: 2014-12-17 14:39:15.077181919 +0800
 Birth: -

sudo stat /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0
stat: cannot stat ‘/usr/lib/x86_64-linux-gnu/libGL.so.1.2.0’: No such file or directory

But

sudo stat /usr/lib/x86_64-linux-gnu/libGL.so.1
  File: ‘/usr/lib/x86_64-linux-gnu/libGL.so.1’ -> ‘libGL.so.10.1.1.28614’
  Size: 21        	Blocks: 0          IO Block: 4096   symbolic link
Device: 802h/2050d	Inode: 3805950     Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2014-12-16 22:42:01.312669993 +0800
Modify: 2014-12-12 02:10:05.880000000 +0800
Change: 2014-12-12 02:10:05.880000000 +0800
 Birth: -
 I’m not using lx-alternative-fglrx, glx-alternative-nvidia or glx-diversions. The libGL.so.10.1.1.28614 is come from my graphic card driver(parallels).

I believe that which file libGL.so.1 link to is system dependent, so that hard code libGL.so to libGL.so.1.2.0 may break in some system. Is there some reasons to use libGL.so.1.2.0 directly rather than libGL.so.1? As your information suggested, libGL.so.1 is pointed to the libGL.so.1.2.0 in normal system without a non-free graphic card driver, and as libGL.so.1 also point to the right file when using a non-free graphic card driver. Will that be more elegant to just put libGL.so to libGL.so.1 so that the package can work across all platforms?

Sincerely,
VXST

> 在 2014年12月17日，上午5:26，Simon McVittie <smcv@debian.org> 写道：
> 
> On Tue, 16 Dec 2014 at 23:59:13 +0800, Shan Ting wrote:
>> libGL.so included in libgl1-mesa-dev has a wrong symlink which refer to a file
>> that's not exist.
> 
> Where does/did the symlink point?
> 
> It seems fine here:
> 
> % dpkg-query -W libgl1-mesa-dev
> libgl1-mesa-dev:amd64	10.3.2-1
> % dpkg-query -W libgl1-mesa-glx
> libgl1-mesa-glx:amd64	10.3.2-1
> libgl1-mesa-glx:i386	10.3.2-1
> % ls -l /usr/lib/x86_64-linux-gnu/libGL.so
> lrwxrwxrwx 1 root root 14 Oct 27 11:44 /usr/lib/x86_64-linux-gnu/libGL.so -> libGL.so.1.2.0
> % ls -l /usr/lib/x86_64-linux-gnu/libGL.so.1
> lrwxrwxrwx 1 root root 14 Oct 27 11:44 /usr/lib/x86_64-linux-gnu/libGL.so.1 -> libGL.so.1.2.0
> % dpkg -L libgl1-mesa-glx:amd64 | grep libGL
> /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0
> /usr/lib/x86_64-linux-gnu/libGL.so.1
> % dpkg -L libgl1-mesa-dev | grep libGL
> /usr/lib/x86_64-linux-gnu/libGL.so
> 
> Do you have glx-alternative-fglrx, glx-alternative-nvidia or glx-diversions
> installed? If you do, please send the output of
> "reportbug --template glx-diversions".
> 
> Regards,
>    S