Skip to content
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

kaldi fails to build with openfst-1.8.3 #4956

Open
yurivict opened this issue Oct 31, 2024 · 3 comments
Open

kaldi fails to build with openfst-1.8.3 #4956

yurivict opened this issue Oct 31, 2024 · 3 comments
Labels

Comments

@yurivict
Copy link

In file included from /usr/ports/audio/kaldi/work/kaldi-4a8b7f6/src/matrix/compressed-matrix.cc:22:
In file included from /usr/ports/audio/kaldi/work/kaldi-4a8b7f6/src/matrix/../matrix/compressed-matrix.h:24:
In file included from /usr/ports/audio/kaldi/work/kaldi-4a8b7f6/src/matrix/../matrix/kaldi-matrix.h:29:
In file included from /usr/ports/audio/kaldi/work/kaldi-4a8b7f6/src/matrix/../matrix/matrix-common.h:26:
In file included from /usr/ports/audio/kaldi/work/kaldi-4a8b7f6/src/matrix/../base/kaldi-common.h:35:
In file included from /usr/ports/audio/kaldi/work/kaldi-4a8b7f6/src/matrix/../base/kaldi-error.h:34:
/usr/ports/audio/kaldi/work/kaldi-4a8b7f6/src/matrix/../base/kaldi-types.h:55:10: fatal error: 'fst/types.h' file not found
   55 | #include <fst/types.h>
      |          ^~~~~~~~~~~~~
1 error generated.

FreeBSD 14.1

@yurivict yurivict added the bug label Oct 31, 2024
@jtrmal
Copy link
Contributor

jtrmal commented Oct 31, 2024 via email

@msqr1
Copy link

msqr1 commented Nov 13, 2024

Add to your compilation command line -DOPENFST_VER=10803. @jtrmal IIRC, we just fake the lack of fst/types.h using our custom one in kaldi-types.h. Specifically, we have this check #if OPENFST_VER >= 10800 to detect if OpenFST is higher than 1.8.0 (doesn't have a fst/types.h anymore). Should we document this better?
@yurivict

@jtrmal
Copy link
Contributor

jtrmal commented Nov 13, 2024

Yeah, but that variable should be already set up automatically, thats why I'm confused. Or is this person also working on the WASM port?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants