Closed sl1pkn07 closed 8 years ago
CL_FLT_EPSILON's error? What the hell have they done?
IDK xd
Your most recent commit fixed the issue. It built without errors. However the packaged version still pumps out the errors listed above.
not at all
g++ -O2 -std=c++11 -Wall -Wno-unused-local-typedefs -I. -I./shared -I./include -march=native -O2 -pipe -fstack-protector-strong -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/vapoursynth -c KNLMeansCL/KNLMeansCL.cpp -o KNLMeansCL/KNLMeansCL.o
In file included from KNLMeansCL/KNLMeansCL.h:41:0,
from KNLMeansCL/KNLMeansCL.cpp:36:
KNLMeansCL/kernel.h:341:119: warning: backslash-newline at end of file
" \n" \
In file included from /usr/include/CL/cl.h:30:0,
from KNLMeansCL/KNLMeansCL.h:38,
from KNLMeansCL/KNLMeansCL.cpp:36:
KNLMeansCL/KNLMeansCL.cpp:789:37: error: exponent has no digits
const cl_float pattern_u3 = CL_FLT_EPSILON;
^
KNLMeansCL/KNLMeansCL.cpp: In function 'const VSFrameRef* VapourSynthPluginGetFrame(int, int, void**, void**, VSFrameContext*, VSCore*, const VSAPI*)':
KNLMeansCL/KNLMeansCL.cpp:789:37: error: unable to find numeric literal operator 'operator""f'
const cl_float pattern_u3 = CL_FLT_EPSILON;
^
KNLMeansCL/KNLMeansCL.cpp:789:37: note: use -std=gnu++11 or -fext-numeric-literals to enable more built-in suffixes
make: *** [GNUmakefile:24: KNLMeansCL/KNLMeansCL.o] Error 1
but if add '-std=gnu++11' to cxxflags build ok(?) (idk why, because https://github.com/Khanattila/KNLMeansCL/blob/master/configure#L91) EDIT: add '-fext-numeric-literals' instead of '-std=gnu++11' also fails EDIT2: change 'c++11' to 'gnu++11' fix build packaged and GIT version O_o (doh!)