Summary: | media-libs/mesa-17.1.0_rc4 (with gcc-6.3.0) - error: no matching function for call to ‘llvm::Argument::addAttr(llvm::AttributeList | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | alexander, jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log and environment |
Description
Juergen Rose
2017-05-15 15:57:16 UTC
Probably because mesa-17.1 is missing this commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=a9d27c8a33a4aef9b71f716cd08ad3d52bc1591c And most likely the combination of mesa-17.1 and llvm-5 will be unsupported by upstream (just like it was with mesa-12.0 and llvm-3.9). The patch of comment 1 helped here to emerge mesa-17.1.0 with gcc-6.3.0. 'emerge =mesa-17.1.1' seems to fail with the same error. Created attachment 475126 [details]
Build log and environment
Comment on attachment 475126 [details]
Build log and environment
Put here by mistake. It is not related to this bug, please remove the attachment.
'emerge =mesa-17.1.2' fails as well. 'emerge =mesa-17.1.3' fails as well. Could the patch of comment 1 not added to the default portage tree? (In reply to Juergen Rose from comment #8) > 'emerge =mesa-17.1.3' fails as well. Could the patch of comment 1 not added > to the default portage tree? No. Stable Mesa versions do not support newer versions of LLVM as an upstream policy. It has always been that way, yet we always get new bug reports like this one. |