Skip to content

Fix ccache configuration issue because it was configured before CUDA #3241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 11, 2022

Conversation

umar456
Copy link
Member

@umar456 umar456 commented Apr 9, 2022

Ccache was configured before CUDA was setup. This caused the launch-nvcc
script to include an empty CUDA_NVCC_EXECUTABLE variable.

Description

Ccache was configured before CUDA was setup. This caused the launch-nvcc
script to include an empty CUDA_NVCC_EXECUTABLE variable.

Changes to Users

N/A

Checklist

  • Rebased on latest master
  • Code compiles
  • Tests pass
  • [ ] Functions added to unified API
  • [ ] Functions documented

umar456 added 2 commits April 9, 2022 14:09
Ccache was configured before CUDA was setup. This caused the launch-nvcc
script to include an empty CUDA_NVCC_EXECUTABLE variable.
The path to some configuration files were relative to CMAKE_MODULE_PATH.
This variable can be a list of strings which causes errors when
CMAKE_MODULE_PATH was modified to include additional values.
syurkevi
syurkevi previously approved these changes Apr 11, 2022
@umar456 umar456 merged commit 590267d into arrayfire:master Apr 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants