| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
RepoMan-Options: --include-arches="amd64"
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The version cap added by 2e80ee40ee74cc3005945355fd1a67ef4347ebbd was
not sufficient to solve Bug #650136 because although it did prevent
Beignet from pulling in slot 6 of sys-devel/llvm and sys-devel/clang
on fresh installations, it did nothing to avoid using these if already
installed. Thanks to the use of llvm.eclass this now no longer happens;
I have just tested this on a system with llvm6 installed and beignet
still ended up using llvm5.
Closes: https://bugs.gentoo.org/650136
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/650136
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default Beignet CMake scripts look for LLVM parameters using
llvm-config regardless of target architecture. For multilib builds on
amd64 against >=sys-devel/llvm-4.0.0 this resulted in the linker being
passed the abi_x86_64 libdir in abi_x86_32 mode, causing "file in wrong
format" errors and build failures.
We now work around this issue by having Beignet's FindLLVM.cmake look
for ${CHOST}-llvm-config instead. Hopefully there will be an official
upstream fix for this at some point.
Closes: https://bugs.gentoo.org/638078
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
|
| |
Gentoo-Bug: 638078
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
Now with support for llvm-4 and llvm-5!
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|