‘logl’ was not declared in this scope

[GoogleCodeExporter]

What steps will reproduce the problem?
1.originally got output described in 
http://code.google.com/p/m2m-aligner/issues/detail?id=1
2.implemented prescribed solution
3.executed 'make'

What is the expected output? What do you see instead?
My output:

g++ -O3 -ffast-math -funroll-all-loops -fpeel-loops -ftracer -funswitch-loops 
-funit-at-a-time -pthread  -c -I./tclap1.1.0/include/   mmEM.cpp -o mmEM.o
g++: unrecognized option '-pthread'
mmEM.cpp: In member function ‘std::vector<long double> 
mmEM::nViterbi_align(param, vector_str, vector_str, vector_2str&, 
vector_2str&)’:
mmEM.cpp:752:73: error: ‘logl’ was not declared in this scope
mmEM.cpp:771:73: error: ‘logl’ was not declared in this scope
mmEM.cpp:801:61: error: ‘logl’ was not declared in this scope
mmEM.cpp: In member function ‘long double mmEM::viterbi_align(param, 
vector_str, vector_str, std::vector<std::basic_string<char> >*, 
std::vector<std::basic_string<char> >*)’:
mmEM.cpp:937:61: error: ‘logl’ was not declared in this scope
mmEM.cpp:954:61: error: ‘logl’ was not declared in this scope
mmEM.cpp:983:49: error: ‘logl’ was not declared in this scope
makefile:23: recipe for target `mmEM.o' failed
make: *** [mmEM.o] Error 1

What version of the product are you using? On what operating system?
Using m2m-aligner v1.0. Running cygwin on windows 7. 
Thread model: posix
gcc version 4.5.3 (GCC)

Please provide any additional information below.

Discovered that 'logl' is in math.h. Included math.h in mmEM.h but still had 
the same issue

Original issue reported on code.google.com by mingxiao...@gmail.com on 24 May 2012 at 12:40

[GoogleCodeExporter]

It's interesting. 'logl' is a standard function which should be in <cmath>. 
It's already included in .h, isn't it?

Well, I'll dig it further. It doesn't appear to be a problem from my side. I 
think it might be something to do with cygwin on windows 7 and its gcc. Let me 
know if you find any solution.

Thanks,
Sittichai

Original comment by jiampojamarn3 on 25 May 2012 at 2:09

[GoogleCodeExporter]

I did some search, and it seems to me that it's because of the gcc 4.5 on 
cygwin itself. Could you try just have a simple problem that uses the log 
function to see if it runs/be able to complied on your side?

or look for more info from the search:
https://www.google.com/webhp?sourceid=chrome-instant&ie=UTF-8#hl=en&sclient=psy-
ab&q=log+undefined+cygwin+gcc+4.5&oq=log+undefined+cygwin+gcc+4.5&aq=f&aqi=&aql=
1&gs_l=serp.3...48270.55916.0.56222.30.30.0.0.0.0.315.4635.4j24j1j1.30.0.cqn%2Cf
ixedpos%3Dfalse%2Cboost_normal%3D40%2Cboost_high%3D40%2Ccconf%3D0-95%2Cmin_lengt
h%3D2%2Crate_low%3D0-015%2Crate_high%3D0-015%2Csecond_pass%3Dfalse.1.0.0.tU3SPC-
kvZ8&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.,cf.osb&fp=9199e6f9bd1dae38&biw=1440&
bih=787

Let met know how it goes. 

Thanks,
Sittichai

Original comment by sittich...@google.com on 29 May 2012 at 5:57

[GoogleCodeExporter]

I meant to say -- a simple program that uses the log function .. 

Sittichai

Original comment by sittich...@google.com on 29 May 2012 at 5:58