I've compiled Monotone 0.40 on lots of platforms recently without any
problems at all, but today I'm faced with a compile problem on a Novell
SUSE SLES 10 box where I got stuck:
| [...]
| if g++ -DLOCALEDIR=\"/tmp/monotone/share/locale\" -DHAVE_CONFIG_H -I. -I. -I.
-I./lua -I./pcre -I/v/sr/sw/include -I/v/sr/sw/include -Wall -W
-Wno-unused -fno-strict-aliasing -MT mtn-app_state.o -MD -MP -MF
".deps/mtn-app_state.Tpo" -c -o mtn-app_state.o `test -f 'app_state.cc' || echo
'./'`app_state.cc; \
| then mv -f ".deps/mtn-app_state.Tpo" ".deps/mtn-app_state.Po"; else rm -f
".deps/mtn-app_state.Tpo"; exit 1; fi
| In file included from app_state.hh:13,
| from app_state.cc:11:
| options.hh:25: error: 'option' is not a template
| options.hh:26: error: type 'option' is not derived from type 'options'
| options.hh:26: error: expected ';' before '<' token
| options.hh:27: error: ISO C++ forbids declaration of 'options_type' with no
type
| options.hh:27: error: expected ';' before 'const'
| options.hh:29: error: 'static_options_fun' was not declared in this scope
| options.hh:29: error: 'static_options_fun' was not declared in this scope
| options.hh:29: error: template argument 1 is invalid
The compiler is GCC 4.2.3 and exactly the same one I've used to build
Monotone 0.40 on all other platforms (because both GCC and Monotone
are inside an OpenPKG software stack). I've no clue why this GCC 4.2.3
under SLES 10 now thinks that the stuff in option.hh no longer defines
the option::option as a template. I've even ensured that the included
option.hh is really the option.hh from the Monotone source tree and the
contained "namespace option { [...] template<typename T> struct option {
... } [...] }" is really used during compilation.
Does someone with deeper C++ knowledge have more clue?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
