-
Notifications
You must be signed in to change notification settings - Fork 247
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
Install kaldi script fails with missing folder #303
Comments
I've added a install_mkl.sh script to the tools directory that should install MKL for you. This would be the fastest option for Intel processors. For AMD, OpenBLAS (https://www.openblas.net/) might be better. I'm a bit surprised that it says "configured to use MKL" even if you don't have it installed - it should figure out by itself what BLAS library you have (MKL, OpenBLAS, ATLAS etc.). Chances are you had none of those installed? |
Yeah, I found that the underlying issue is this package requires Intel's MKL library. I have installed OpenBLAS and Atlas in the past, but if those were still installed, why would it error out? I also found this blog which lead to me this Intel page on installing their MKL Ubuntu repo. That allowed me to easily install MKL with:
After that, the However, pykaldi is still broken, and running:
In my Python3.9 virtualenv gives me the error:
|
Have you sourced path.sh as described in the README?
source path.sh
Either you have kaldi installed in the current working dir where you run
python or you need to change the paths in path.sh.
Pykaldi is probably not finding your Kaldi installation.
…On Sun, May 29, 2022, 2:55 PM Chris Spencer ***@***.***> wrote:
Yeah, I found that the underlying issue is this package requires Intel's
MKL library. I have installed OpenBLAS and Atlas in the past, but if those
were still installed, why would it error out?
I also found this blog <https://deepakbaby.in/post/kaldi-mkl/> which lead
to me this Intel page on installing their MKL Ubuntu repo
<https://www.intel.com/content/www/us/en/develop/documentation/installation-guide-for-intel-oneapi-toolkits-linux/top/installation/install-using-package-managers/apt.html>
.
That allowed me to easily install MKL with:
wget -O- https://apt.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS.PUB | gpg --dearmor | sudo tee /usr/share/keyrings/oneapi-archive-keyring.gpg > /dev/null
echo "deb [signed-by=/usr/share/keyrings/oneapi-archive-keyring.gpg] https://apt.repos.intel.com/oneapi all main" | sudo tee /etc/apt/sources.list.d/oneAPI.list
sudo apt update
sudo apt install intel-basekit
After that, the ./install_kaldi.sh finally completed without error.
However, pykaldi is still broken, and running:
python -c "from kaldi.asr import NnetLatticeFasterRecognizer"
In my Python3.9 virtualenv gives me the error:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/project/.env/lib/python3.9/site-packages/kaldi/__init__.py", line 14, in <module>
from . import base
File "/project/.env/lib/python3.9/site-packages/kaldi/base/__init__.py", line 1, in <module>
from ._kaldi_error import *
ImportError: /project/.env/lib/python3.9/site-packages/kaldi/base/_kaldi_error.so: undefined symbol: _ZN5kaldi25g_abort_on_assert_failureE
—
Reply to this email directly, view it on GitHub
<#303 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACKGA6X5KPQT3IL2RHATSM3VMNSLFANCNFSM5XHIURFQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
If I do that, it just gives me a different error:
|
What OS and version are you using? I guess your glibc is too old. It should work on ubuntu 20.04, it has glibc 2.31, your distro must be older than that. |
I'm running Ubuntu 18.04 and Python3.9. |
I have GLIBC 2.27 installed. Is there any way to get it to work with that? |
You will need to compile your own pykaldi version then and optionally make
your own whl. Or upgrade to 20.04.
…On Sun, May 29, 2022, 7:57 PM Chris Spencer ***@***.***> wrote:
I have GLIBC 2.27 installed. Is there any way to get it to work with that?
—
Reply to this email directly, view it on GitHub
<#303 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACKGA6SK6DAIODJIFVST5HLVMOVXPANCNFSM5XHIURFQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Ok, I upgraded to Ubuntu 20.04, and that fixed the glibc error. Seems to be working now. The only caveat I'm seeing is it only seems to work from inside the
Is there any work around for this? Not a huge deal, but it would be nice to not have to limit my application to CDing into that directory. My total install script to get a working Kaldi environment turned out to be:
Am I missing a step? |
Just a FYI, you don't need: ./check_dependencies.sh If you are installing from a whl package |
The
./install_kaldi.sh
script mentioned in the README fails with the following error:Presumably, I'm missing the undocumented library MKL. Where/how should I install that?
The text was updated successfully, but these errors were encountered: