From: Arnab G. <ar...@gm...> - 2013-07-31 12:26:53
|
Kaldi needs some kind of linear algebra library. ATLAS is easily obtained. Otherwise if your system has MKL, you could use that as well. Check to see what messages install_atlas.sh generated (btw, you are using an older version, since the install_atlas.sh has now moved to tools/extras). The most common problem is that CPU throttling needs to be disabled for installing ATLAS, but that requires root access. It may be best to consult with your admin about ATLAS/MKL and to install one if none is present. -Arnab On Mon, Jul 29, 2013 at 1:35 AM, Ji He <jv...@uw...> wrote: > Hi there, > > I heard that Kaldi is becoming popular these days and I want to try it > myself. But I don't have access to root directory in my lab's machine, so I > try to install it on my local space (and setting file dependencies etc.). I > am not sure how to do this. > > Basically when I ran the normal installation steps, I got errors in > ./configure (in src/), it says: > > On Linux: Checking for linear algebra header files ... > Using ATLAS as the linear algebra library. > Could not find libatlas.a in any of the obvious places... will try dynamic > libraries. > No libatlas.so in /usr/lib > No libatlas.so in /usr/lib/atlas > No libatlas.so in /usr/lib/atlas-sse2 > No libatlas.so in /usr/lib/atlas-sse3 > No libatlas.so in /usr/lib64 > No libatlas.so in /usr/lib64/atlas > No libatlas.so in /usr/lib64/atlas-sse2 > No libatlas.so in /usr/lib64/atlas-sse3 > No libatlas.so in /usr/local/lib > No libatlas.so in /usr/local/lib/atlas > No libatlas.so in /usr/local/lib/atlas-sse2 > No libatlas.so in /usr/local/lib/atlas-sse3 > No libatlas.so in /usr/local/lib64 > No libatlas.so in /usr/local/lib64/atlas > No libatlas.so in /usr/local/lib64/atlas-sse2 > No libatlas.so in /usr/local/lib64/atlas-sse3 > No libatlas.so in > /s1/jvking/temp/Kaldi/kaldi-trunk/src/../tools/ATLAS/build/install/lib/ > No libatlas.so in /s1/jvking/temp/Kaldi/kaldi-trunk/tools/ATLAS/lib > Could not find libatlas.so in any of the obvious places. > ** Failed to configure ATLAS lbiraries *** > ** ERROR ** > **Configure cannot proceed automatically, but by editing kaldi.mk > ** you may be able to proceed (replace [somewhere] with a directory), > ** or install the ATLAS package on your machine, > ** or try going to ../tools and running install_atlas.sh, and running > ** this script (configure) again. > > I read how Kaldi is compiled and it seems I may need to edit the > > ATLASINC = [somewhere]/include > ATLASLIBS = [somewhere]/liblapack.a [somewhere]/libcblas.a > [somewhere]/libatlas.a [somewhere]/libf77blas.a > > lines in src/kaldi.mk, but I don't know where I should pointed it to. I also > tried running ./tools/install_atlas.sh but have no idea what I should do > after that step. I cannot find libatlas.a anywhere in my local directory, > i.e. kaldi-trunk. I look forward to your quick reply. > > With regards, > HE Ji > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > |