Am Sonntag 20 September 2015, 17:46:05 schrieb Guillaume Munch:
> If you configure again it should enable c++11 which is now activated by
> default for "known good compilers".
Unfortunately, recompiling (after make distclean) does not help.
> This is still a bug because it has been decided that 2.2 will have to be
> written in two standards: c++98 and c++11. But it should solve the issue
> for you (unless you have a reason for using the --disable-cxx11 option)
> while I work on the issue.
>
> Now and until 2.3, every commit has to be tested with the option
> --disable-cxx11. My bad for forgetting to do so.
I have not explicitly disabled c++11, and it seems to use it:
Configuration
Host type: i686-pc-linux-gnu
Special build flags: build=development warnings assertions stdlib-debug
concept-checks c++11 use-aspell use-enchant use-hunspell
C++ Compiler: g++ (4.8)
C++ Compiler flags: -Wall -Wextra -g -O -std=c++11
C++ Compiler user flags:
Linker flags:
Linker user flags:
Qt Frontend:
Qt version: 4.8.6
Packaging: posix
LyX binary dir: /usr/local/bin
LyX files dir: /usr/local/share/lyx-svn
Jürgen
