Emerging media-gfx/imagemagick with 'opencl' USE flag has NVidia drivers dependency regardless ATI video card. (VIDEO_CARDS="fglrx") Reproducible: Always Steps to Reproduce: 1. USE="opencl" emerge imagemagick Actual Results: has x11-drivers/nvidia-drivers ebuild in dependencies. Expected Results: At least doesn`t have NVidia drivers hardcoded, or even depend on packages that correspond to videocard.
The only provider for opencl in portage is nvidia-drivers afaik but I've improved the logic in 6.7.3.0 now
Please change ebuilds to this: opencl? ( video_cards_nvidia? ( x11-drivers/nvidia-drivers >=dev-util/nvidia-cuda-toolkit-3.1 ) ) And ati-drivers has opencl-libraries, too!! So this is NOT FIXED. :)
just a heads up the latest ati-drivers-11.12 1)do have a openCL flag 2) since ati started shipping their openCL implementation with their driver. so you might want to change the ebuild logick to depend on either (with the openCL flag) of course 3) just a friendly notification that might hit in a large scale later when openCL gets more common.
some issues: - i don't have any box to test imagemagick with ati-drivers, only own boxes with nvidia-drivers and cards - the "m4/ax_opencl.m4" macro from which imagemagicks's configure is generated looks NVidia specific, so upstream isn't likely testing it with ati-drivers either so any change to the ebuild logic must come from the ati-drivers maintainers, who aren't listening this bug
(In reply to comment #2) no. the opencl stack has to get this fixed in common code so that ebuilds can start depending on that. otherwise we get a broken build when we enable USE=opencl. further, trying to do USE=opencl on a system that doesn't provide opencl binaries makes no sense. so disable USE=opencl in your make.conf. if pulling in nvidia packages drives home the point that USE=opencl only works with nvidia, then so be it.
*** This bug has been marked as a duplicate of bug 322161 ***
