Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#46357 - [lib32-llvm-libs] llvm 3.7.0+ crashes Mesa radeonsi (maybe not only) drivers

Attached to Project: Community Packages
Opened by Maxim Sheviakov (mradermaxlol) - Saturday, 19 September 2015, 17:07 GMT
Last edited by Laurent Carlier (lordheavy) - Saturday, 19 September 2015, 17:51 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
LLVM 3.7.0+ crashes Mesa. Actually, installing llvm-libs >= 3.7.0 causes Mesa to fail loading radeonsi_dri.so and other radeon drivers + swrast.so, thus even display manager crashes on start.

Additional info:
package version - llvm and related packages (clang, lldb etc.) are 3.7.0-1 from testing repo. Multilib version also has this issues - lib32-clang, lib32-llvm and lib32-llvm-libs are 3.7.0-1. I am using Mesa 11.0.0 release built from source, but these errors occur with 10.6.7 and 10.6.6 too.
logs - glxinfo:
(begin)
name of display: :0
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: GLXBadContext
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 47
Current serial number in output stream: 46
(end)


Steps to reproduce:
1) Install mesa and some DE
2) Install llvm and all related stuff (llvm-libs, clang, clang-analyzer, clang-tools-extra + lib32-llvm, lib32-llvm-libs, lib32-clang)
3) Reboot your system
4) Enjoy the stop/error screen :)
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Saturday, 19 September 2015, 17:51 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#46352 

Loading...