-
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
tools/extras/check_dependencies.sh libtool issues #223
Comments
In debian-jessie the libtool package has been split. So an additional package has to be installed to get the libtool binary. The package libtool-bin has to be added to tools/check_dependencies.sh script. I will add modify tools/check_dependencies.sh to do a debian version dependent package check. |
Everything in tools/ builds without libtool-bin being installed, by the way. None of the configure scripts need the libtool binary directly (as the bug you linked to said, it is rare for it to be necessary). If you're already special-casing Debian I would suggest looking for libtoolize instead. |
Thanks. @jtrmal: I notice when experimenting with extras/install_irstlm.sh that Dan On Fri, Oct 9, 2015 at 3:00 PM, dwks notifications@github.com wrote:
|
After another glance at this, it seems this issue was resolved by Dan -- and I resolved the readlink issue later, so I'm closing it. |
One more issue: running "make" from a clean install in tools/ on Debian 8.2 fails because check_dependencies thinks I need the binary "libtool". It seems Debian now has "libtoolize" in the libtool package which generates local "libtool"s (zeromq/libzmq#1385), and this is used by e.g. openfst's configure script. The full build works correctly if I check for "libtoolize" instead of "libtool" in tools/extras/check_dependencies.sh.
Otherwise, if I run "make" three separate times (or make -k) the build mostly completes, although it does not make the openfst symlink, so I have to make it myself or configure kaldi with --fst-root pointing at the right place. Note: there is also a Debian package "libtool-bin" which provides a system-wide "libtool" executable, and installing that will make the build succeed, although I don't think the executable is actually used because local "libtool"s are still created.
Maybe it would be best to test for either libtool or libtoolize. I'm not very familiar with autotools unfortunately.
Last comment: when building tools/ in parallel with make -j N, the check_dependencies is run at the same time as other configure scripts etc, which makes its output interleaved and difficult to spot. This will run check_dependencies first even if multiple jobs were specified:
The text was updated successfully, but these errors were encountered: