Am Montag, 13. Juni 2016 um 17:49:07, schrieb Jean-Marc Lasgouttes <lasgout...@lyx.org> > Le 13/06/2016 à 17:34, Kornel Benko a écrit : > >> The posting you refer to seems to imply that it is a C++14 problem. What > >> about enforcing C++11 mode instead? > > > > Hm, yes. But if we want to support 'std::make_unique' we need C++14 test. > > At least, that was my impression while working with 4.8 and 5.3.1 g++ > > versions. > > > > I tried to enforce c++11, everything compiled. Apparently you are right. > > At least we have a usable test for whether we can turn on c++14 mode. > Does it work with gcc 4.8? It might be that clang can only do c++14 when > using its own libc++. > > > I don't understand, why _my_ clang 3.6 accepts parameter '-std=c++14'. > > I am not sure that I understand your question.
Here example (without source file)
gcc4.8
# g++ -std=c++14
g++: error: unrecognized command line option ‘-std=c++14’
g++: fatal error: no input files
compilation terminated.
gcc 5.3.1
# /usr/local/gcc5.3/bin/g++ -std=c++14
g++: fatal error: no input files
compilation terminated.
clang 3.6
# /usr/lib/llvm-3.6/bin/clang++ -std=c++14
clang: error: no input files
> JMarc
So, clang accepts this parameter, but does not define std::make_unique.
Kornel
signature.asc
Description: This is a digitally signed message part.
