On Jul 6, 2015, at 4:45 PM, Stephan Witt <st.w...@gmx.net> wrote:
>> 
>> The process failed with these apparent C++ errors:
> 
> I think I've seen these errors with Xcode 6 and the accompanying clang 
> compiler.
> It has something to do with cxx11 if I'm not mistaken. Sorry, I forgot the 
> details.
> I'm on Xcode 5 and Mac OS X 10.8.6 for my daily work.

I'm on OS X 10.9.5 and Xcode 5.1.1 so maybe it's not an Xcode issue. These 
problems appear to be either C coding errors or a clang error. In either case 
it will stop my build efforts because I don't know how to write C etc. FWIW I 
still have an older Xcode, 3.2.6, at /Developer/Applications/Xcode.app.

Should I report a bug for this?

Jerry

> 
>> /Applications/Xcode.app/Contents/Developer/usr/bin/make  install-am
>> make[7]: Nothing to be done for `install-exec-am'.
>> make[7]: Nothing to be done for `install-data-am'.
>> Making install in .
>> make[6]: Nothing to be done for `install-exec-am'.
>> make[6]: Nothing to be done for `install-data-am'.
>> Making install in .
>> CXX      CutAndPaste.o
>> CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
>>               pars.insert(next(pars.begin(), pit),
>>                           ^~~~
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>  note: 
>>     candidate function [with _ForwardIter = 
>> std::__1::__list_iterator<lyx::Paragraph, void *>]
>> next(_ForwardIter __x,
>> ^
>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>     std::__1::__list_iterator<lyx::Paragraph, void *>, Diff = long]
>> inline It next(It i, Diff n = 1)
>>         ^
>> CutAndPaste.cpp:398:15: error: call to 'next' is ambiguous
>>               pars.insert(next(pars.begin(), pit + 1),
>>                           ^~~~
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>  note: 
>>     candidate function [with _ForwardIter = 
>> std::__1::__list_iterator<lyx::Paragraph, void *>]
>> next(_ForwardIter __x,
>> ^
>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>     std::__1::__list_iterator<lyx::Paragraph, void *>, Diff = long]
>> inline It next(It i, Diff n = 1)
>>         ^
>> CutAndPaste.cpp:602:26: error: call to 'next' is ambiguous
>>       ParagraphList copy_pars(next(pars.begin(), startpit),
>>                               ^~~~
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>  note: 
>>     candidate function [with _ForwardIter = 
>> std::__1::__list_const_iterator<lyx::Paragraph, void
>>     *>]
>> next(_ForwardIter __x,
>> ^
>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>     std::__1::__list_const_iterator<lyx::Paragraph, void *>, Diff = long]
>> inline It next(It i, Diff n = 1)
>>         ^
>> 3 errors generated.
>> make[4]: *** [CutAndPaste.o] Error 1
>> make[3]: *** [install-recursive] Error 1
>> make[2]: *** [install] Error 2
>> make[1]: *** [install-recursive] Error 1
>> make: *** [install-strip] Error 2
>> 
>> 
>> 
>> 
>> These notwithstanding, it looks like there could be Qt problems later. I 
>> spotted the following lines:
>> 
>> checking whether Qt5 is requested... no
>> 
>> and
>> 
>> Configuration
>> ...
>> Qt Frontend:
>>     Qt version:         4.8.7
>> ...
>> 
>> Qt 4.8.7 is my MacPorts installation.
>> 
>> FWIW, I see that in config.log, this appears:
>> 
>> --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt 
>> Creator.app/Contents/Frameworks/
>>                                                         ^ note space
>> 
>> Notice that the quotes from my script have been removed.
> 
> Yes, that's the difference between the ideal and the real world.
> Unix is able to handle spaces in path names as long as nobody makes a mistake.
> One has to quote every path name variable in scripts - it is not automatic.
> Since the configure script is generated by auto tools I think it would be
> easier to solve it pragmatically instead of getting it right.
> 
> The practical solution is to rename your Qt Creator application name and
> remove the space from path name. I think it doesn't break the app -
> at least it should not.
> 
> Regards, Stephan

Reply via email to