-
Notifications
You must be signed in to change notification settings - Fork 546
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
onnx_backend_test.py libnvonnxparser.so.0: cannot open shared object file #43
Comments
Maybe you could add |
I've also encountered this error with TRT5.0.2GA when trying to run the tests (Also trying to build the TRT examples fails)
|
@bpinaya you should make sure that |
Thanks for the reply @Faldict, do we have to add it to the python path or something? It did build successfully and I installed the libraries with |
@bpinaya do you also install the python modules? |
I have, this is the output of
But the error persists still, even from the C api, I was trying to build some onnx samples with cpp api (sampleOnnxMNIST) from tensorrt samples I get:
So I really ran out of ideas. Doing it on a fresh install of my OS was my last option but I'm thinking about that. |
@bpinaya I don't know what happened due to the uninformative logs. You can find my versions here: |
Apologies, we had some uninformative installation instructions for previous versions of TensorRT. Have you tried using the latest version of TensorRT (7.2.1) available on the master branch and following the build instructions there? |
Closing due to inactivity - if you are still having issues with the latest version of onnx-tensorrt feel free to open a new issue. |
Hi
After I make the project, I encountered
No module named '_nv_onnx_parser_bindings'
error (same as 29)so I import sys and sys.path.append('/home/onnx-tensorrt/build/lib.linux-x86_64-3.5/onnx_tensorrt/parser/'),
and now the new error is this
The libnvonnxparser.so.0 is in onnx-tensorrt/build but I can't get the path to work.
Any advise? Thanks!
The text was updated successfully, but these errors were encountered: