OpenBLAS error compiling

515 views
Skip to first unread message

jessy bris

unread,
Sep 13, 2019, 4:48:07 AM9/13/19
to kaldi-developers
I am trying to install Kaldi. I run extras/check_dependencies.sh, is indicate that the OpenBLAS is not detected.
I run extras/install_openblas.sh , the following error is indicated:

ar: strmm_kernel_LN.o: No such file or directory
../Makefile.tail:40: recipe for target 'libs' failed
make[1]: *** [libs] Error 1
make[1]: Leaving directory '/home/user/Bureau/kaldi/tools/OpenBLAS/kernel'
Makefile:133: recipe for target 'libs' failed
make: *** [libs] Error 1
make[1]: Leaving directory '/home/user/Bureau/kaldi/tools/OpenBLASl'

I see in xianyi's page to solve this problem I should run: make clean , make TARGET=Hashwell and make BINARY=32 next build. I do these steps, I get:

OpenBLAS build complete. (BLAS CBLAS LAPACK LAPACKE)


OS ... Linux

Architecture ... x86

BINARY ... 32bit

C compiler ... GCC (command line : cc)

Fortran compiler ... GFORTRAN (command line : gfortran)

Library Name ... libopenblas_nehalemp-r0.3.5.a (Multi threaded; Max num-threads is 4)


Generating openblas_config.h in /opt/OpenBLAS/include

Generating f77blas.h in /opt/OpenBLAS/include

Generating cblas.h in /opt/OpenBLAS/include

Copying LAPACKE header files to /opt/OpenBLAS/include

Copying the static library to /opt/OpenBLAS/lib

Copying the shared library to /opt/OpenBLAS/lib

Generating openblas.pc in /opt/OpenBLAS/lib/pkgconfig

Generating OpenBLASConfig.cmake in /opt/OpenBLAS/lib/cmake/openblas

Generating OpenBLASConfigVersion.cmake in /opt/OpenBLAS/lib/cmake/openblas

Install OK!


But when i run again extras/check_dependencies.sh , i get the same problem:

OpenBLAS not detected. Run extras/install_openblas.sh
 
Please may you help me to solve the problem. Thank You

Jan Trmal

unread,
Sep 13, 2019, 4:55:21 AM9/13/19
to kaldi-developers
It's Haswell, not Hashwell (probably won't help)
Often time, nowadays, machines do not support 32bit binaries/libs (and you wouldn't be able to compile 64bit kaldi together with 32bit OpenBLAS.
So IMO, you should try
 make clean && make TARGET=Haswell && make BINARY=64
y.

--
visit http://kaldi-asr.org/forums.html to find out how to join.
---
You received this message because you are subscribed to the Google Groups "kaldi-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kaldi-develope...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kaldi-developers/d87a5b04-f273-442f-b16b-0d710deb8193%40googlegroups.com.

jessy bris

unread,
Sep 13, 2019, 6:45:52 AM9/13/19
to kaldi-developers
Hello Yenda! Thank you for response

I tried to make these steps, but i have always the same problem. I can not install the OpenBLAS.  I get the same error:



ar: strmm_kernel_LN.o: No such file or directory
../Makefile.tail:40: recipe for target 'libs' failed
make[1]: *** [libs] Error 1
make[1]: Leaving directory '/home/user/Bureau/kaldi/
tools/OpenBLAS/kernel'
Makefile:145: recipe for target 'libs' failed

make: *** [libs] Error 1
make[1]: Leaving directory '/home/user/Bureau/kaldi/tools/OpenBLAS'
To unsubscribe from this group and stop receiving emails from it, send an email to kaldi-de...@googlegroups.com.

Jan Trmal

unread,
Sep 13, 2019, 7:06:14 AM9/13/19
to kaldi-developers
there might be an error before this (when making strmm_kernel_LN.o)
Other than that, no idea -- ask the OpenBLAS people.
y.


To unsubscribe from this group and stop receiving emails from it, send an email to kaldi-develope...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kaldi-developers/03e00816-7bff-4a47-b02b-5af226370ae2%40googlegroups.com.

Daniel Povey

unread,
Sep 14, 2019, 1:33:46 AM9/14/19
to kaldi-developers
Check where Kaldi is looking for the OpenBLAS installation directory
(look in the configure script). It is configurable by args to that
script.
I believe our Kaldi installation script installs OpenBLAS locally (in
a subdir of kaldi/tools/), not at the system level, so probably the
default in the `configure` script does not match where it was installed.

Dan
> To view this discussion on the web visit https://groups.google.com/d/msgid/kaldi-developers/CAFReZQaf4LPpQLYWXEOCVfZaBr3Ya21D%3DS9%2Bq9GZH9fTFv1O%2BQ%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages