Skip to content
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

Cupy Import Error. #969

Closed
Xiaofei-Wang opened this issue Jul 17, 2019 · 1 comment
Closed

Cupy Import Error. #969

Xiaofei-Wang opened this issue Jul 17, 2019 · 1 comment
Labels
Bug bug should be fixed

Comments

@Xiaofei-Wang
Copy link
Contributor

Does someone have the cupy import error during making the ESPnet?
For example, if I
make KALDI=/path/to/kaldi CUDA_VERSION=9.0
The cupy 6.0 still tries to find libraries of CUDA 10.0 on default, although I have correctly set the environment.

Instead of using
cupy.done: espnet.done ifneq ($(strip $(CUPY_VERSION)),) . venv/bin/activate && pip install cupy==$(CUPY_VERSION) touch cupy.done endif

I have to manually change the code to
cupy.done: espnet.done ifneq ($(strip $(CUPY_VERSION)),) . venv/bin/activate && pip install cupy-cuda90==$(CUPY_VERSION) touch cupy.done endif

I would suggest making a small modification of the Makefile: )

@sw005320 sw005320 added the Bug bug should be fixed label Jul 17, 2019
@sw005320
Copy link
Contributor

Thanks for the report.
If so, it would be better to switch to use cupy-cuda80, cupy-cuda90, cupy-cuda100, etc.(?)
Hmm, this is not so cool option.

Xiaofei-Wang added a commit to Xiaofei-Wang/espnet that referenced this issue Jul 31, 2019
ShigekiKarita added a commit that referenced this issue Jul 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug bug should be fixed
Projects
None yet
Development

No branches or pull requests

3 participants