When doing an emerge -C intel-ocl-sdk-2.0.31360 I noticed that several symbolic links get left in /usr/lib after package removal, pointing to non-existent files. They are;
/usr/lib64/libcl_logger.so -> OpenCL/vendors/intel/libcl_logger.so
/usr/lib64/libclang_compiler.so -> OpenCL/vendors/intel/libclang_compiler.so
/usr/lib64/libclbltfne9.so -> OpenCL/vendors/intel/libclbltfne9.so
/usr/lib64/libclbltfnh8.so -> OpenCL/vendors/intel/libclbltfnh8.so
/usr/lib64/libclbltfnu8.so -> OpenCL/vendors/intel/libclbltfnu8.so
/usr/lib64/libclbltfny8.so -> OpenCL/vendors/intel/libclbltfny8.so
/usr/lib64/libcpu_device.so -> OpenCL/vendors/intel/libcpu_device.so
/usr/lib64/libintelocl.so -> OpenCL/vendors/intel/libintelocl.so
/usr/lib64/libtask_executor.so -> OpenCL/vendors/intel/libtask_executor.so
Those files are not related to intel-ocl-sdk per se, but to eselect opencl. After uninstalling intel ocl you should choose new opencl implementation and those files will be gone
Thanks for the clarification.
To be clear this condition existed after I had removed the opencl USE flag from my environment, and run emerge --depclean, which removed not only;
Based on your clarification I'm not sure if upon removal of virtual/opencl-0-r2 whether these links should be removed or not so, I just manually removed them.
(In reply to comment #2)
> Thanks for the clarification.
> To be clear this condition existed after I had removed the opencl USE flag
> from my environment, and run emerge --depclean, which removed not only;
> but also
> Based on your clarification I'm not sure if upon removal of
> virtual/opencl-0-r2 whether these links should be removed or not so, I just
> manually removed them.
They're created outside of portage, that's why they're left behind after you uninstall app-admin/eselect-opencl. TBH I don't know how to deal with it. I thinkg I'd need to craft something clever in pkg_postrm.