From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 78242] Steam cannot load mesa drivers (libGL error: driver pointer missing)
Date: Mon, 12 May 2014 17:46:40 +0000 [thread overview]
Message-ID: <bug-78242-502-4MwqC979Zb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-78242-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 7258 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=78242
--- Comment #4 from Daniel Scharrer <daniel@constexpr.org> ---
> It's a steam bug, not a mesa one
I disagree: this (naïvely linking LLVM) is a change in mesa that breaks many
binary software packages, not just Steam. While the steam-runtime will likely
get a fix for this at some point, some older games may not be so lucky.
Packaging libstdc++ and libgcc_s is relatively common with binary software
packages targeting Linux - it is practically required in order to target a wide
range of distribution versions while not limiting yourself to an ancient
compiler. Here is a small list of such packages that I happen to have installed
which bundle those libraries:
$ find /{opt,usr/local/games}/ ~/Games/Trine/ -name 'libstdc++*' -o -name
'libgcc_s*'
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/intel64/pinruntime/libgcc_s.so
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/intel64/pinruntime/libstdc++.so
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/intel64/pinruntime/libstdc++.so.6
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/intel64/pinruntime/libstdc++.so.6.0.10
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/intel64/pinruntime/libgcc_s.so.1
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/ia32/pinruntime/libgcc_s.so
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/ia32/pinruntime/libstdc++.so
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/ia32/pinruntime/libstdc++.so.6
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/ia32/pinruntime/libstdc++.so.6.0.10
/opt/intel/composerxe-2013.2.144/bin/sourcechecker/lib/ia32/pinruntime/libgcc_s.so.1
/opt/quake4/libstdc++.so.6
/opt/quake4/libgcc_s.so.1
/usr/local/games/sacred/lib/lib1/libstdc++.so.6
/usr/local/games/sacred/lib/lib1/libgcc_s.so.1
/usr/local/games/x2/lib/lib1/libstdc++.so.6
/usr/local/games/x2/lib/lib1/libgcc_s.so.1
/usr/local/games/postalx/postal2game/System/libstdc++.so.5
/usr/local/games/postalx/postal2game/System/libgcc_s.so.1
/usr/local/games/postalx/postal1game/libstdc++.so.5
/usr/local/games/postalx/postal1game/libgcc_s.so.1
/usr/local/games/aquaria/libstdc++.so.6
/usr/local/games/aquaria/libgcc_s.so.1
/usr/local/games/lugaru/libstdc++.so.6
/usr/local/games/lugaru/libgcc_s.so.1
/usr/local/games/survivor/lib32/libstdc++.so.6
/usr/local/games/survivor/lib32/libgcc_s.so.1
/usr/local/games/shadowgrounds/lib32/libstdc++.so.6
/usr/local/games/shadowgrounds/lib32/libgcc_s.so.1
/usr/local/games/coldwar/lib/libstdc++.so.6
/usr/local/games/coldwar/lib/libstdc++.so.6.0.8
/usr/local/games/postal2/System/libstdc++.so.5
/usr/local/games/postal2/System/libgcc_s.so.1
/usr/local/games/braid/libstdc++.so.6
/usr/local/games/braid/libgcc_s.so.1
/usr/local/games/testtool/lib/lib1/libstdc++.so.6
/usr/local/games/testtool/lib/lib1/libgcc_s.so.1
/usr/local/games/prey/libstdc++.so.5
/usr/local/games/prey/libgcc_s.so.1
/home/dscharrer/Games/Trine/lib32/libgcc_s.so.1
/home/dscharrer/Games/Trine/lib32/libstdc++.so.6
/home/dscharrer/Games/Trine/lib64/libstdc++.so.6
This has not been a problem in the past as system libraries (those you
effectively have to link against to make full use of the hardware) have
refrained from pulling in either of the GCC libraries. In fact, the only one I
found doing this besides mesa is XvMC:
$ for f in /lib/lib{dl,m,c,rt}.* /usr/lib/libasound* /usr/lib/libX*
/usr/lib/libxcb* /usr/lib/mesa/* /usr/lib/opengl/{ati,xorg-x11}/lib/libGL*
/usr/lib/libpulse* ; do ldd $f | grep -P '(libgcc|libstdc++)' | sed "s|^|$f: |"
; done
/usr/lib/libXvMCr600.so: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007fb39b72e000)
/usr/lib/libXvMCr600.so: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007fb39ae6c000)
/usr/lib/libXvMCr600.so.1: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007f45d4a8f000)
/usr/lib/libXvMCr600.so.1: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007f45d41cd000)
/usr/lib/libXvMCr600.so.1.0.0: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007fc235d72000)
/usr/lib/libXvMCr600.so.1.0.0: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007fc2354b0000)
/usr/lib/mesa/r200_dri.so: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007ff45e80e000)
/usr/lib/mesa/r200_dri.so: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007ff45df4c000)
/usr/lib/mesa/r300g_dri.so: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007f69359b7000)
/usr/lib/mesa/r300g_dri.so: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007f69350f5000)
/usr/lib/mesa/r600g_dri.so: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007f37f0e61000)
/usr/lib/mesa/r600g_dri.so: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007f37f059f000)
/usr/lib/mesa/radeon_dri.so: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007f5528868000)
/usr/lib/mesa/radeon_dri.so: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007f5527fa6000)
/usr/lib/mesa/radeonsi_dri.so: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007f4021a96000)
/usr/lib/mesa/radeonsi_dri.so: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007f40211d4000)
/usr/lib/mesa/swrast_dri.so: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007f3bf7cc8000)
/usr/lib/mesa/swrast_dri.so: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007f3bf7406000)
/usr/lib/mesa/swrastg_dri.so: libstdc++.so.6 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libstdc++.so.6
(0x00007fd0b4263000)
/usr/lib/mesa/swrastg_dri.so: libgcc_s.so.1 =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0-pre9999/libgcc_s.so.1
(0x00007fd0b39a1000)
This search includes fglrx's libGL by the way: The proprietary AMD (and I'm
sure NVIDIA) drivers have long used C++ internally, but have taken care not to
pollute the global namespace with the C++ standard library or GCC helper
library. I think this shows even more precedent that these libraries should not
be considered safe to use in base system libraries without additional
precautions.
What you are doing here is introducing additional problems where none existed
before. Please reconsider statically linking libLLVM and required C++/GCC libs
into *_dri.so or finding some other solution to not conflict with programs
loading libGL. (An even stricter RTLD_LOCAL that completely namespaces libs
would be nice to have here …)
For reference, here are a few more bugs caused by this:
#30192, #30901, #38182, #38783, #43964, #66955
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 8246 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-12 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 6:21 [Bug 78242] New: Steam cannot load mesa drivers (libGL error: driver pointer missing) bugzilla-daemon
2014-05-04 8:44 ` [Bug 78242] " bugzilla-daemon
2014-05-04 8:45 ` bugzilla-daemon
2014-05-07 21:00 ` bugzilla-daemon
2014-05-07 22:01 ` bugzilla-daemon
2014-05-12 17:46 ` bugzilla-daemon [this message]
2014-05-12 22:49 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-78242-502-4MwqC979Zb@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox