widelands-dev team mailing list archive

[Tibor Bamhor <tiborb95@xxxxxxxxx>]

I have installed:

ii  clang                                1:3.0-6.2
              i386         Low-Level Virtual Machine (LLVM), C language
family frontend
ii  clang-format-3.5                     1:3.5~svn198086-1~exp1
             i386         Tool to format C/C++/Obj-C code
ii  libclang-common-dev                  1:3.0-6.2
              i386         clang library - Common development package
ii  libllvm3.0:i386                      3.0-10
             i386         Low-Level Virtual Machine (LLVM), runtime library
ii  libllvm3.5:i386                      1:3.5~svn198086-1~exp1
             i386         Modular compiler and toolchain technologies,
runtime library
ii  llvm-3.0                             3.0-10
             i386         Low-Level Virtual Machine (LLVM)
ii  llvm-3.0-dev                         3.0-10
             i386         Low-Level Virtual Machine (LLVM), libraries and
headers
ii  llvm-3.0-runtime                     3.0-10
             i386         Low-Level Virtual Machine (LLVM), bytecode
interpreter


as for http://libcxx.llvm.org/  if the package should be named "libc++" - I
dont have such and no such package is available in my current
repositories...
Or perhaps the package is?

libstdc++6 - GNU Standard C++ Library v3


Tibor


2014-06-16 12:16 GMT+02:00 Holger Rapp <HolgerRapp@xxxxxxx>:

>
> src/logic/widelands.h:68:19: error: constexpr variable 'INVALID_INDEX'
> must be initialized by a constant
>       expression
> constexpr uint8_t INVALID_INDEX = std::numeric_limits<uint8_t>::max();
>
>
> seems like you are not using the http://libcxx.llvm.org/ which you should
> always use with clang. It defines max to be a constexpr.
>
>
> It was fixed with adding 255 instead
> of std::numeric_limits<uint8_t>::max();
>
> and second problem:
>
> src/ui_fsmenu/loadreplay.cc:221:68: error: use of undeclared identifier
> 'fn'
>                        [](const std::string& fn) {return
> boost::ends_with(fn, REPLAY_SUFFIX);});
>
>
> that makes no sense to me. Seems like a clang bug. Which clang version is
> that?
>
>