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

can not run "from nvidia.dali.pipeline import Pipeline" #5

Closed
xxradon opened this issue Jun 22, 2018 · 9 comments
Closed

can not run "from nvidia.dali.pipeline import Pipeline" #5

xxradon opened this issue Jun 22, 2018 · 9 comments
Assignees

Comments

@xxradon
Copy link

xxradon commented Jun 22, 2018

when I use the 3.1. Binary Installation step [In]( https://docs.nvidia.com/deeplearning/sdk/dali-install-guide/index.html ,everything is ok.But when I 'get started',in python ,run this command" from nvidia.dali.pipeline import Pipeline",I got this error:'ImportError: libdali.so: cannot open shared object file: No such file or directory
'

@JanuszL
Copy link
Contributor

JanuszL commented Jun 22, 2018

Hi,
Could you tell us which python version do you use?
Can you check status of following command:
pip show nvidia-dali
grab the path from Location:
ls LOCATION/nvidia/dali/.libs/

@cliffwoolley
Copy link
Contributor

I found an error in the RPATH updating in bundle-wheel.sh that likely accounts for this. I have a fix pending.

@cliffwoolley
Copy link
Contributor

(It would still help to know the answers to @JanuszL 's questions so that I can attempt to reproduce the problem. Further: are you using virtualenv or Conda environments or any similar setup?)

@cliffwoolley cliffwoolley self-assigned this Jun 23, 2018
@JiangPQ
Copy link

JiangPQ commented Jun 23, 2018

Hi, I got a similar problem. Here is the traceback:

Traceback (most recent call last):
File "/home/xxxxx/PycharmProjects/torch90/111.py", line 500, in
from nvidia.dali.pipeline import Pipeline
File "/home/xxxxx/miniconda3/envs/torch90/lib/python3.6/site-packages/nvidia/dali/init.py", line 17, in
from . import ops
File "/home/xxxxx/miniconda3/envs/torch90/lib/python3.6/site-packages/nvidia/dali/ops.py", line 19, in
from nvidia.dali import backend as b
File "/home/xxxxx/miniconda3/envs/torch90/lib/python3.6/site-packages/nvidia/dali/backend.py", line 15, in
from nvidia.dali.backend_impl import *
ImportError: libnppicom.so.9.0: cannot open shared object file: No such file or directory

The lib64 has been added to LD_LIBRARY_PATH and everything goes fine when I run pytorch so i think CUDA9.0 is properly installed.

echo $LD_LIBRARY_PATH
/usr/local/cuda/lib64:/opt/intel/compilers_and_libraries_2018.2.199/linux/ipp/lib/intel64

I use conda environment BTW and this is what pip show nvidia-dali gives:

$ pip show nvidia-dali
Name: nvidia-dali
Version: 0.1.0
Summary: NVIDIA DALI
Home-page: https://github.com/NVIDIA/dali
Author: NVIDIA Corporation
Author-email: UNKNOWN
License: Apache License 2.0
Location: /home/xxxxx/miniconda3/envs/torch90/lib/python3.6/site-packages
Requires: future
Required-by:

@cliffwoolley

@xxradon
Copy link
Author

xxradon commented Jun 23, 2018

@JanuszL @cliffwoolley
I also use conda environment and this is what pip show nvidia-dali gives:

Name: nvidia-dali
Version: 0.1.1
Summary: NVIDIA DALI
Home-page: https://github.com/NVIDIA/dali
Author: NVIDIA Corporation
Author-email: UNKNOWN
License: Apache License 2.0
Location: /home/shining/ProgramFiles/miniconda/envs/pytorch/lib/python3.6/site-packages
Requires: future

I have search libdali.so in my conda env ,I found nothing.But when I compiled from DALI source,I got the libdali.so.
And @JiangPQ,I think your cuda environment got something wrong,you can test your pytorch cuda to verify.

@JanuszL
Copy link
Contributor

JanuszL commented Jun 24, 2018

@xxradon
Could you also:
ls /home/shining/ProgramFiles/miniconda/envs/pytorch/lib/python3.6/site-packages/nvidia/dali/.libs/ ?

@cliffwoolley
Copy link
Contributor

It's not called libdali.so in the installed binary package; it's libdali-*.so, where the * is a hash. Bundle-wheel.sh renames it when packaging the wheel. But because of some path errors, not all references to it are corrected properly. I have a fix for that, but the fix exposes another error that I'm still trying to sort out.

@xxradon
Copy link
Author

xxradon commented Jun 28, 2018

I have test recent release editon,this problem has been fixed.Thank you.

@xxradon xxradon closed this as completed Jun 28, 2018
@cliffwoolley
Copy link
Contributor

Actually this isn't fixed yet. :) Glad it worked for you regardless, but I'm reopening this until I push the proper fix.

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

No branches or pull requests

4 participants