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!
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!
FS#34638 - [mesa] Needs to be built with llvm shared libs
Attached to Project:
Arch Linux
Opened by Marcin Rzeźnicki (mrzeznicki) - Saturday, 06 April 2013, 12:33 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 06 April 2013, 14:27 GMT
Opened by Marcin Rzeźnicki (mrzeznicki) - Saturday, 06 April 2013, 12:33 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 06 April 2013, 14:27 GMT
|
DetailsBuilding mesa packages without --with-llvm-shared-libs is most probably the source of https://bugs.archlinux.org/task/34040 (currently closed, marked upstream), https://bugs.freedesktop.org/show_bug.cgi?id=61364, https://bugs.freedesktop.org/show_bug.cgi?id=59334 and possibly other llvm related bugs in mesa drivers. Please see the discussion here for the details: http://lists.freedesktop.org/archives/mesa-dev/2013-January/032944.html. Most recent mesa 9.1.1-1 has this option commented out with quite unconvincing explanation:
# --with-llvm-shared-libs \ # enabling this would force us to move llvm-amdgpu-snapshot from community to extra, delay it until llvm 3.3 / Mesa 9.2/10.0 Thanks in advance |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Saturday, 06 April 2013, 14:27 GMT
Reason for closing: Not a bug
Additional comments about closing: the explenation says all. we can't have two different llvm versions in one repo with the same files. llvm 3.3 will bring this change.
Saturday, 06 April 2013, 14:27 GMT
Reason for closing: Not a bug
Additional comments about closing: the explenation says all. we can't have two different llvm versions in one repo with the same files. llvm 3.3 will bring this change.