For dev-util/nvidia-cuda-toolkit-5.0.35 with x86_64-pc-linux-gnu-4.5.4 set as gcc default postinst posted the following message: WARN: postinst gcc >= 4.5 will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like /usr/*pc-linux-gnu/gcc-bin/gcc4.5 to the nvcc compiler flags This is the expected behavior of cause. After setting the gcc default to x86_64-pc-linux-gnu-4.6.3 and reemering nvidia-cuda-toolkit-5.0.35-r1 postinst showed: WARN: postinst gcc >= will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like /usr/*pc-linux-gnu/gcc-bin/gcc to the nvcc compiler flags So something went wrong during postinst. 'cuda-config -s' shows '4.6' on my system. This is more or less a cosmetically problem and doesn't effects the functionality. Reproducible: Always Expected Results: Don't show a warning during pkg_postinst() if gcc >= 4.6 is used.
The code in that section had wrong logic. should be fixed now. +*nvidia-cuda-toolkit-5.0.35-r2 (22 Jan 2013) +*nvidia-cuda-toolkit-4.2.9-r2 (22 Jan 2013) + + 22 Jan 2013; Justin Lecher <jlec@gentoo.org> + +nvidia-cuda-toolkit-4.2.9-r2.ebuild, +nvidia-cuda-toolkit-5.0.35-r2.ebuild: + Correct postinst msg logic; fine grade deletion of files +
