-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Build fails, kaldi.mk: No such file or directory #3395
Comments
Looks like a bug in their install script, you shouldn't be running "make
clean" before "configure", swapping them might work.
…On Sun, Jun 16, 2019 at 6:49 AM Alex ***@***.***> wrote:
I'm trying to build a gentle aligner based on kaldi
lowerquality/gentle#224
<lowerquality/gentle#224>
Recently authors were not very responsive, so I'm asking about the problem
here.
I'm building the docker image (you may see what prereq are installed in
unbuntu 18.04)
https://github.com/lowerquality/gentle/blob/master/Dockerfile
*The image build fails while building kaldi.* There used a specific
commit of kaldi, I tried with the recent version, a like result.
Script used to build kaldi (
https://github.com/lowerquality/gentle/blob/master/ext/install_kaldi.sh):
#!/bin/bash
# Prepare Kaldi
cd kaldi/tools
make clean
make
./extras/install_openblas.sh
cd ../src
make clean
./configure --static --static-math=yes --static-fst=yes --use-cuda=no --openblas-root=../tools/OpenBLAS/install
make depend
cd ../../
Build takes quite a while, but completes with an error:
make[2]: Leaving directory '/gentle/ext/kaldi/tools/OpenBLAS/exports'
OpenBLAS build complete. (BLAS CBLAS LAPACK LAPACKE)
OS ... Linux
Architecture ... x86_64
BINARY ... 64bit
C compiler ... GCC (command line : cc)
Fortran compiler ... GFORTRAN (command line : gfortran)
Library Name ... libopenblas_nehalem-r0.3.7.dev.a (Single threaded)
To install the library, you can run "make PREFIX=/path/to/your/installation install".
make -j 2 -f Makefile.install install
make[2]: Entering directory '/gentle/ext/kaldi/tools/OpenBLAS'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
Generating openblas_config.h in /gentle/ext/kaldi/tools/OpenBLAS/install/include
Generating f77blas.h in /gentle/ext/kaldi/tools/OpenBLAS/install/include
Generating cblas.h in /gentle/ext/kaldi/tools/OpenBLAS/install/include
Copying LAPACKE header files to /gentle/ext/kaldi/tools/OpenBLAS/install/include
Copying the static library to /gentle/ext/kaldi/tools/OpenBLAS/install/lib
Copying the shared library to /gentle/ext/kaldi/tools/OpenBLAS/install/lib
Generating openblas.pc in /gentle/ext/kaldi/tools/OpenBLAS/install/lib/pkgconfig
Generating OpenBLASConfig.cmake in /gentle/ext/kaldi/tools/OpenBLAS/install/lib/cmake/openblas
Generating OpenBLASConfigVersion.cmake in /gentle/ext/kaldi/tools/OpenBLAS/install/lib/cmake/openblas
Install OK!
make[2]: Leaving directory '/gentle/ext/kaldi/tools/OpenBLAS'
make[1]: Leaving directory '/gentle/ext/kaldi/tools/OpenBLAS'
Makefile:30: kaldi.mk: No such file or directorykaldi.mk does not exist; you have to run ./configure
Makefile:96: recipe for target 'kaldi.mk' failed
make: *** [kaldi.mk] Error 1
Configuring KALDI to use OPENBLAS
Configuring ...
Checking compiler g++ ...
Checking OpenFst library in ...
***configure failed: Could not find file /include/fst/fst.h:
you may not have installed OpenFst. See ../tools/INSTALL ***
Makefile:30: kaldi.mk: No such file or directorykaldi.mk does not exist; you have to run ./configure
Makefile:96: recipe for target 'kaldi.mk' failed
make: *** [kaldi.mk] Error 1
Makefile:5: kaldi/src/kaldi.mk: No such file or directory
Not building with cuda!!!
make: *** No rule to make target 'kaldi/src/kaldi.mk'. Stop.
The command '/bin/sh -c export MAKEFLAGS=' -j8' && cd /gentle/ext && ./install_kaldi.sh && make depend && make && rm -rf kaldi *.o' returned a non-zero code: 2
[image: image]
<https://user-images.githubusercontent.com/736697/59559074-95018e00-9019-11e9-84dd-23e4c0d60bdc.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3395?email_source=notifications&email_token=AAZFLO6UO6KNHM3IXB4SGZLP2YLDXA5CNFSM4HYQ4Z2KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZXS6UA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAZFLO3FHOQFGK7U3HW67W3P2YLDXANCNFSM4HYQ4Z2A>
.
|
Well I change it too:
But result is the same. |
I recommend that you follow kaldi's own install instructions rather than that setup. |
I've managed to build on google cloud 1vCPU vm, with no |
I found an answer in another forum which tells that OpenFst official changed their route, |
I unsucessfully tried editing their
this failed, so I'm trying to build kaldi manually and will see if I can get gentle to use that. |
I ran out of memory on my VPS... |
Looks like you need an instance with more memory.
…On Fri, Oct 4, 2019 at 3:21 AM Péter Finta ***@***.***> wrote:
I ran out of memory on my VPS... virtual memory exhausted: Cannot
allocate memory, so I'll have to put this on hold for now.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#3395?email_source=notifications&email_token=AAZFLOZEYX6OB2OTW44DISLQM2D7HA5CNFSM4HYQ4Z2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAJ7GDI#issuecomment-538178317>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAZFLO3CAJMJHAVIWOI2VRLQM2D7HANCNFSM4HYQ4Z2A>
.
|
I'm trying to build a gentle aligner based on kaldi
lowerquality/gentle#224
Recently authors were not very responsive, so I'm asking about the problem here.
I'm building the docker image (you may see what prereq are installed in unbuntu 18.04)
https://github.com/lowerquality/gentle/blob/master/Dockerfile
The image build fails while building kaldi. There used a specific commit of kaldi, I tried with the recent version, a like result.
Script used to build kaldi (https://github.com/lowerquality/gentle/blob/master/ext/install_kaldi.sh):
Build takes quite a while, but completes with an error:
The text was updated successfully, but these errors were encountered: