Summary: | app-emulation/wine-1.4_rc2: fails to compile, OpenCL 32-bit development files not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | DrSlony <bugs> |
Component: | [OLD] Unspecified | Assignee: | Wine Maintainers <wine> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | candrews, theli.ua |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
DrSlony
2012-02-11 19:42:53 UTC
Created attachment 301591 [details]
build.log
Adding "app-emulation/wine -opencl" to package.use lets the compilation proceed succesfully, however I opened this bug report because I don't think doing this should be necessary. What version of nvidia-drivers and eselect-opencl are you using? Does the failure still occur after running "eselect opencl set nvidia"? If the failure still occurs, please give the output of the following commands: ls -l /usr/lib*/libOpenCL* equery files nvidia-drivers | grep OpenCL (If you do not have equery, you will need to install app-portage/gentoolkit.) (In reply to comment #2) > Adding "app-emulation/wine -opencl" to package.use lets the compilation proceed > succesfully, however I opened this bug report because I don't think doing this > should be necessary. The only reason you had to add "app-emulation/wine -opencl" to package.use is because you globally enabled the opencl USE flag in your /etc/make.conf ;) x11-drivers/nvidia-drivers-290.10-r1 app-admin/eselect-opencl-0.0.2 "Does the failure still occur after running "eselect opencl set nvidia"?" Yes ls -l /usr/lib*/libOpenCL* lrwxrwxrwx 1 root root 14 Feb 14 13:56 /usr/lib32/libOpenCL.so -> libOpenCL.so.1 lrwxrwxrwx 1 root root 14 Feb 14 13:56 /usr/lib64/libOpenCL.so -> libOpenCL.so.1 lrwxrwxrwx 1 root root 14 Feb 14 13:56 /usr/lib/libOpenCL.so -> libOpenCL.so.1 Blinking, so I guess not found. equery files nvidia-drivers | grep OpenCL /etc/OpenCL /etc/OpenCL/vendors /etc/OpenCL/vendors/nvidia.icd /usr/lib32/OpenCL /usr/lib32/OpenCL/vendors /usr/lib32/OpenCL/vendors/nvidia /usr/lib32/OpenCL/vendors/nvidia/libOpenCL.so /usr/lib32/OpenCL/vendors/nvidia/libOpenCL.so.1 /usr/lib32/OpenCL/vendors/nvidia/libOpenCL.so.1.0.0 /usr/lib32/OpenCL/vendors/nvidia/libcuda.so /usr/lib32/OpenCL/vendors/nvidia/libcuda.so.1 /usr/lib32/OpenCL/vendors/nvidia/libcuda.so.290.10 /usr/lib32/OpenCL/vendors/nvidia/libnvidia-compiler.so /usr/lib32/OpenCL/vendors/nvidia/libnvidia-compiler.so.1 /usr/lib32/OpenCL/vendors/nvidia/libnvidia-compiler.so.290.10 /usr/lib64/OpenCL /usr/lib64/OpenCL/vendors /usr/lib64/OpenCL/vendors/nvidia /usr/lib64/OpenCL/vendors/nvidia/libOpenCL.so /usr/lib64/OpenCL/vendors/nvidia/libOpenCL.so.1 /usr/lib64/OpenCL/vendors/nvidia/libOpenCL.so.1.0.0 /usr/lib64/OpenCL/vendors/nvidia/libcuda.so /usr/lib64/OpenCL/vendors/nvidia/libcuda.so.1 /usr/lib64/OpenCL/vendors/nvidia/libcuda.so.290.10 /usr/lib64/OpenCL/vendors/nvidia/libnvidia-compiler.so /usr/lib64/OpenCL/vendors/nvidia/libnvidia-compiler.so.1 /usr/lib64/OpenCL/vendors/nvidia/libnvidia-compiler.so.290.10 (In reply to comment #4) > x11-drivers/nvidia-drivers-290.10-r1 > app-admin/eselect-opencl-0.0.2 > > "Does the failure still occur after running "eselect opencl set nvidia"?" > Yes > > ls -l /usr/lib*/libOpenCL* > lrwxrwxrwx 1 root root 14 Feb 14 13:56 /usr/lib32/libOpenCL.so -> > libOpenCL.so.1 > lrwxrwxrwx 1 root root 14 Feb 14 13:56 /usr/lib64/libOpenCL.so -> > libOpenCL.so.1 > lrwxrwxrwx 1 root root 14 Feb 14 13:56 /usr/lib/libOpenCL.so -> libOpenCL.so.1 > Blinking, so I guess not found. This problem was almost certainly caused by using a buggy pre-release of eselect-opencl taken from some random overlay. After you do the following: * rm /usr/lib*/libOpenCL.so * update to eselect-opencl-1.1.0 from portage * eselect opencl set nvidia it should all work :) In the future, I recommend using "emerge --deep" to tell portage to update the entire dependency tree of whatever you are emerging (eselect-opencl is an indirect dependency of wine). See the portage man page for more information. *** Bug 403947 has been marked as a duplicate of this bug. *** I'm not using nvidia drivers - I'm using Intel drivers. I'm also not using any pre-release overlays, and today was the first time eselect-opencl was installed on my system. # eselect opencl list Available OpenCL implementations: [1] intel * # emerge eselect-opencl virtual/opencl dev-util/intel-ocl-sdk -pv [ebuild R ] app-admin/eselect-opencl-1.1.0 0 kB [ebuild R ] virtual/opencl-0-r1 VIDEO_CARDS="-fglrx -nvidia" 0 kB [ebuild R ] dev-util/intel-ocl-sdk-1.5 0 kB (In reply to comment #7) > I'm not using nvidia drivers - I'm using Intel drivers. I'm also not using any > pre-release overlays, and today was the first time eselect-opencl was installed > on my system. > > # eselect opencl list > Available OpenCL implementations: > [1] intel * > > > # emerge eselect-opencl virtual/opencl dev-util/intel-ocl-sdk -pv > [ebuild R ] app-admin/eselect-opencl-1.1.0 0 kB > [ebuild R ] virtual/opencl-0-r1 VIDEO_CARDS="-fglrx -nvidia" 0 kB > [ebuild R ] dev-util/intel-ocl-sdk-1.5 0 kB Then #403947 is not a duplicate of this bug, so I have confirmed and reopened it. I do run emerge -NuDv world once a week. I updated eselect-opencl to 1.1.0 and opencl to 0-r1 and it works fine now. |