Bug 1885 - The location of libGL.so has been changed in Ubuntu 11.10.
Summary: The location of libGL.so has been changed in Ubuntu 11.10.
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.2 M2
Assignee: Edwin Zhai
QA Contact:
URL:
Whiteboard: patch out: Jan13
Depends on:
Blocks: 1886
  Show dependency tree
 
Reported: 2012-01-08 19:02 UTC by Hongna Xu
Modified: 2012-03-09 06:44 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hongna Xu 2012-01-08 19:02:02 UTC
The new location is: /usr/lib/x86_64-linux-gnu/libGL.so for X86-64 machine.
The log followed:
===========================================================
WARNING: distccd not present, no distcc support loaded.
WARNING: nVidia proprietary OpenGL libraries detected.
nVidia's OpenGL libraries are known to have compatibility issues with qemu,
resulting in a segfault. Please uninstall these drivers or ensure the mesa libGL
libraries precede nvidia's via LD_PRELOAD(Already do it on Ubuntu).
Skip nVidia's libGL on Ubuntu!
Running qemu...
...
...
...
ERROR: ld.so: object '/usr/lib/libGL.so' from LD_PRELOAD cannot be preloaded: ignored.
Enabling opengl
Set 'tap0' nonpersistent
Releasing lockfile of preconfigured tap device 'tap0'
Comment 1 Jiajun Xu 2012-01-08 23:54:07 UTC
Without libGL.so, with Hongna's Ubuntu 11.10 system, qemu could start up but if we run glxgear command, qemu will segfault.
Comment 2 Saul Wold 2012-01-10 08:50:02 UTC
It seems there is a check in runqemu for /usr/lib/*-linux-gnu/libGL.so, but in the runqemu-internal it hard code adds /usr/lib/libGL.so to the GL_LD_PRELOAD list. We should be passing or re-check where the library resides to runqemu-internal.
Comment 4 Hongna Xu 2012-03-09 06:44:57 UTC
Verify the bug as fixed with poky/1.2_M3 branch, commit 320558f494c618f53e0c773db3ea0109476e8359.