[Faiss] Fix dependencies#18780
Conversation
|
|
|
@NancyLi1013 yup, saw that build break, it went green now :) |
|
LGTM now, have you tested the feature |
|
@NancyLi1013 good point, I added a small fix to the port file for gpu. That said faiss[gpu] does not build for me locally, regardless of any changes. I'm getting nvcc compiler errors such as: There are others. In terms of CMake targets, the gpu feature should be fine, as the dependency is declared as: so it should not generate absolute paths. I'm not sure if the CI builds test faiss[gpu], but in case the failure to compile the cuda code is more general than on my machine, I think it should be split out from this PR / issue. |
|
|
|
@NancyLi1013 no I cannot build |
|
I was blocked by the failure on my local with master branch. Have you tried with master branch on your machine? Does it work? If you have the same problem with the changes on this PR, it might not be the new issue introduced by this PR. |
|
@NancyLi1013 yup, I am getting the same cuda compiler not found error on master. Seems to be common, as other ports have fixes for it. It looks like you can't get to compiling cuda on master until you make changes and fix the cuda compiler like I have in the portfile in this PR. I don't think my changes broke the faiss[cuda] - I think it was simply broken from the start and not tested on CI. |
|
Thanks for your efforts and patience. @bucurb |
|
Thanks for the PR! |
Describe the pull request
What does your PR fix?
Fixes [faiss] The target files on x64-linux contain absolute paths #18776
Which triplets are supported/not supported? Have you updated the CI baseline?
all previously supported, No
Does your PR follow the maintainer guide?
Yes
If you have added/updated a port: Have you run
./vcpkg x-add-version --alland committed the result?Yes
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/