AdolfVonKleist / Phonetisaurus

Phonetisaurus G2P
BSD 3-Clause "New" or "Revised" License
449 stars 122 forks source link

Configuration error #10

Closed dmbuchta closed 7 years ago

dmbuchta commented 8 years ago

I configured openfst like so: sudo ./configure --enable-static --enable-shared --enable-far \ --enable-lookahead-fsts --enable-const-fsts --enable-pdt \ --enable-ngram-fsts --enable-linear-fsts CC=gcc-4.9 and then installed it. But I still get a configuration error when trying to configure Phonetisaurs: configure: error: Can't find one or more extensions. OpenFst should have been configured with the following flags: --enable-static --enable-shared --enable-far --enable-lookahead-fsts --enable-const-fsts --enable-pdt --enable-ngram-fsts --enable-linear-fsts

dthomas888 commented 8 years ago

I had the same problem. its fails the configuration check because libfstlinearscript.so is not generated in /usr/local/lib/fst all other extensions have been created.

openFST may have changed the names of the linear .so files to linear_tagger-fst.so, fst/linear_classifier-fst.so.

take a look at http://www.openfst.org/twiki/bin/view/FST/FstExtensions you can see the generated filenames for linear-fsts are different then the other extensions.

I added the new extension name to the configure file to get past the extension check. now I get this error.

configure: WARNING: OpenFst headers do not appear to be patched. Did you apply the Kaldi OpenFst patch? Might be problematic when using with Kaldi. configure: creating ./config.status config.status: creating Makefile

PaulPoveda commented 8 years ago

Hello everyone,

I get the same error as dmbuchta and I had installed OpenFst 1.4 and I got the same error :

Found OpenFst headers. configure: WARNING: OpenFst headers do not appear to be patched. Did you apply the Kaldi OpenFst patch? Might be problematic when using with Kaldi. configure: creating ./config.status config.status: creating Makefile

Any solution for this ?

imrehg commented 8 years ago

Regarding the original issue, looks like those files were searched for e.g. in /usr/local/lib/fst, while in fact they live in /usr/local/lib/ directly (at least it's there on my Debian system). My solution was to symlink them to be also available in the fst subdirectory, i.e.:

# cd /usr/local/lib
# for f in libfst*; do ln -s "../$f" "fst/$f"; done

After this the configuration succeeds.

brownedon commented 8 years ago

Thanks imrehg, the links work for me on a Raspberry PI 3.

DanSilvaDev commented 7 years ago

Hi, I got the same error and tried exactly what @imrehg suggested, but I had no success at all :/ I'm also using raspberry pi 3.

I tried to force the command ./configure --with-openfst-includes=/usr/local/include --with-openfst-libs=/usr/local/lib/

My last try was with openfst 1.4.2, but before, i tried with 1.5.3 and the same message appears.

Any light would be apreciated . Thank you.

dapperfu commented 7 years ago

The problem comes with these 2 lines:

            -a -e "$with_openfst_libs/fst/libfstlookahead.so" \
            -a -e "$with_openfst_libs/fst/libfstlinearscript.so"; then :

It doesn't look like those are installed on later versions.

I tried cutting it out. It made the make file but the make failed.

AdolfVonKleist commented 7 years ago

These two lines are removed now, as they are not actual requirements for the phonetisaurus - they are used with other programs that integrate with OpenFst for various purposes. I believe this should be resolved in the kaldi tag, and in master at this point, at least for OpenFst v1.6.x.

We can reopen if there is still something pending.

rmachad5 commented 6 years ago

@dmbuchta how exactly did you fix this issue? I'm trying to install openfst 1.4.1 and getting same issue and have tried the numerous different configure combos and can't seem to find an answer.

AdolfVonKleist commented 6 years ago

Still a problem with 1.6.x or still a problem with 1.4.x? There are some breaking changes in the transition. I can probably give some hints/feedback to specifics on 1.4.x but I'd rather not try to simultaneously support it.

RuABraun commented 6 years ago

Sorry it was an issue on my end (therefore deleted the comment).