-
Notifications
You must be signed in to change notification settings - Fork 56
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
Not able to run the example on Ubuntu 16.04 #33
Comments
Just add LD_LIBRARY_PATH environment containing the path where this shared-object of kaldi installation is. |
Same here on Ubuntu 18.04 . Python 3.6.9 (default, Nov 7 2019, 10:44:02)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from kaldiasr.nnet3 import KaldiNNet3OnlineModel
>>> kaldi_model = KaldiNNet3OnlineModel('path/to/model_dir')
Intel MKL FATAL ERROR: Cannot load libmkl_avx2.so or libmkl_def.so. As @RaniRaven writes:
Finding and adding $ export LD_PRELOAD=/opt/intel/mkl/lib/intel64/libmkl_avx2.so
$ python3
python3: symbol lookup error: /opt/intel/mkl/lib/intel64/libmkl_avx2.so: undefined symbol: mkl_sparse_optimize_bsr_trsm_i8 Ok, something is missing here. Let's add all $ export LD_PRELOAD=$(ls /opt/intel/mkl/lib/intel64/*.so | tr '\n' ':')
$ python3
python3: symbol lookup error: /opt/intel/mkl/lib/intel64/libmkl_tbb_thread.so: undefined symbol: _ZN3tbb4task13note_affinityEt What exactly should |
I had exactly the same problem. This worked for me:
Source: https://www.bountysource.com/issues/81528572-intel-mkl-fatal-error-cannot-load-libmkl_def-so |
Thanks @hjpulakka. This is working on my system now. |
That LD_PRELOAD location didn't work for me. this did:
|
@sravani40 This depends on how you launch your python program. If you using the terminal (with bash) you can simply add these lines to your |
ImportError: libkaldi-decoder.so: cannot open shared object file: No such file or directory.
Can you share simple steps to do on ubuntu 16.04 && g++ 5.4.0 to run the basic demo?
The text was updated successfully, but these errors were encountered: