What steps will reproduce the problem?
1../autogen.sh
2.make
Error messages:
src/NgramModel.cpp:325: error: call of overloaded 'pow(int, int)' is ambiguous
/usr/include/bits/mathcalls.h:154: note: candidates are: double pow(double,
double)
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/cmath:345:
note: float std::pow(float, float)
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/cmath:349:
note: long double std::pow(long double, long double)
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/cmath:353:
note: double std::pow(double, int)
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/cmath:357:
note: float std::pow(float, int)
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/cmath:361:
note: long double std::pow(long double, int)
make[1]: *** [src/NgramModel.lo] Error 1
make[1]: Leaving directory `/home/wyz/lm/mitlm-0.4.1'
make: *** [all-recursive] Error 1
Solution
Changed src/NgramModel.cpp:325 from
assert(prob <= std::pow(10, -99));
to
assert(prob <= std::pow(10.0, -99.0));
Again, rum `make'
Error message
make[1]: *** No rule to make target `lbfgs.lo', needed by `libmitlm.la'. Stop.
make[1]: Leaving directory `/home/wyz/lm/mitlm-0.4.1'
make: *** [all-recursive] Error 1
Solution,
according to http://code.google.com/p/mitlm/issues/detail?id=26
Change Makefile and Makefile.in
Error message
./.libs/libmitlm.so: undefined reference to `__cxa_get_exception_ptr'
collect2: ld returned 1 exit status
make[1]: *** [evaluate-ngram] Error 1
make[1]: Leaving directory `/home/wyz/lm/mitlm-0.4.1'
make: *** [all-recursive] Error 1
Then I have no idea about how to solve this problem.
What version of the product are you using? On what operating system?
mitlm-0.4.1.tar.gz
Description: Red Hat Enterprise Linux Server release 5.8 (Tikanga)
autoconf (GNU Autoconf) 2.69 (the original version is 2.59)
Please provide any additional information below.
Original issue reported on code.google.com by erzhen...@gmail.com on 16 Jun 2014 at 4:34
Original issue reported on code.google.com by
erzhen...@gmail.com
on 16 Jun 2014 at 4:34