Le 17/02/2016 11:41, Stephan Witt a écrit :
You are not answering my question :) The question was "does it
allow to compile .m files in C++11 mode?“
It looks like I didn’t know the answer. Perhaps I shouldn’t have give
an answer :)
So, could you tell me what happens when you do (with my first patch)
cd src/support && make AppleSpeller.o
I'd like to apply it if it does what it is supposed to do: fix
compilation of .m files in C++11 mode.
Patrick, did you try it?
As far as your other compile problems are concerned, let's start
from the end : the errors in LyX headers.
First idea: look at the Update 4 here:
http://stackoverflow.com/questions/17849154/where-is-definition-of-stdfunction-in-clang-3-3-xcode
Do you suffer from the same issue (an extra version of llvm installed
via hombrew?)
No I don’t have installed homebrew. I don’t like beer - I’m having a
preference for wine.
If it does not work, second idea: pass the flag " -stdlib=libc++"
to select the libc++ library instead of the old gcc lisbstdc++ that
Apple is shipping
http://stackoverflow.com/questions/9345271/xcode-4-3-and-c11-include-paths
With the attached patch I have this error and many more errors:
In file included from
/Users/stephan/git/lyx/src/support/debug.cpp:17: In file included
from /Users/stephan/git/lyx/src/support/../support/FileName.h:19: In
file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/set:387:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/__tree:17:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/stdexcept:70:32:
error: reference to 'string' is ambiguous explicit logic_error(const
string&);
What does your config.h look like? Do you have USE_LLVM_LIBCPP defined?
Can I see the corresponding config.log?
(I have extended this line: cxx11_flags="-std=c++11 -stdlib=libc++“)
I am not 100% sure that it works.
What exactly is the bug I did work around? Is it correct to expect
working C++11 support?
That's the whole point. If C++11 is the default, it is because we expect
it to work. In 2.3, it will be mandatory.
PS. The indentation of lyxinclude.m4 is not nice. This makes it hard
to read with my favorite editor vi.
This file is indeed a mess.
JMarc
