Closed jakirkham closed 4 years ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
Upstreaming this into nvcc
with PR ( https://github.com/conda-forge/nvcc-feedstock/pull/26 ). Once integrated, we can drop this workaround.
As CUDA 10.1 moves some headers and libraries from
/usr/local/cuda
to/usr
, we need to adjust our search strategy for finding them. Sincecudatoolkit
already contains the libraries and is available during the build, this is less of an issue. However we still need to point the compiler to the headers in/usr/include
. Thus we add/usr/include
to our compiler flags. To avoid clobbering other search paths we care about, we make sure to add/usr/include
last. As we are not searching/usr/lib64
, this shouldn't result in any accidental linkages against system libraries.Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)Fixes https://github.com/conda-forge/cupy-feedstock/issues/3