Stephan Witt wrote:

> Hi Lyxers,
> 
> this is Mac OS X 10.6.8 with
> $ g++ -v
> Using built-in specs.
> Target: i686-apple-darwin11
> Configured with:
> /private/var/tmp/llvmgcc42/llvmgcc42-2336.11~28/src/configure
> --disable-checking --enable-werror
> --prefix=/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2
> --mandir=/share/man --enable-languages=c,objc,c++,obj-c++
> --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/
> --with-slibdir=/usr/lib --build=i686-apple-darwin11
> --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.11~28/dst-
llvmCore/Developer/usr/local
> --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11
> --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
> Thread model: posix gcc version 4.2.1 (Based on Apple Inc. build 5658)
> (LLVM build 2336.11.00)
> 
> ...
>   CXX      trivstring.o
> In file included from
> /Users/stephan/git/lyx/src/support/trivstring.cpp:13:
> /Users/stephan/git/lyx/src/support/../support/trivstring.h:66: error:
> expected ‘,’ or ‘...’ before ‘>’ token
> /Users/stephan/git/lyx/src/support/../support/trivstring.h:65: error:
> wrong number of template arguments (1, should be 3)
> /Users/stephan/git/lyx/src/support/../support/strfwd.h:46: error: provided
> for ‘template<class Char, class Traits, class Alloc> struct
> std::basic_string’
> /Users/stephan/git/lyx/src/support/../support/trivstring.h:66: error:
> default argument missing for parameter 3 of ‘lyx::trivial_string<Char>
> lyx::trivial_string<Char>::substr(size_t, size_t, std::char_traits<Char>,
> std::allocator<Char>) const’
> /Users/stephan/git/lyx/src/support/../support/trivstring.h:66: error:
> default argument missing for parameter 4 of ‘lyx::trivial_string<Char>
> lyx::trivial_string<Char>::substr(size_t, size_t, std::char_traits<Char>,
> std::allocator<Char>) const’

This looks very strange. It works here on linux both with g++ 4.7 and 
clang++ 3.5, and I do not see anything wrong from manual inspection. Does it 
work if you combine line 65 and 66 into a single line? Maybe the parser does 
not like the line break inside the type definition?


Georg

Reply via email to