Bernd Mathiske created MESOS-1029:
-------------------------------------

             Summary: lib stout compile errors on Ubuntu 13.10 with Clang 3.5
                 Key: MESOS-1029
                 URL: https://issues.apache.org/jira/browse/MESOS-1029
             Project: Mesos
          Issue Type: Bug
          Components: build, libprocess
         Environment: Ubuntu 13.10
Clang 3.5 (built from source)
            Reporter: Bernd Mathiske
            Assignee: Bernd Mathiske
            Priority: Minor


Depends on MESOS-1009. Will not show unless the former is fixed first.
Fix for this issue is available, will submit for review. 
Compile errors:

../../3rdparty/libprocess/3rdparty/stout/include/stout/os.hpp:730:18: error: 
'va_start' has undefined behavior with
      reference types [-Werror,-Wvarargs]
  va_start(args, fmt);
                 ^
/root/clang/build/Release/bin/../lib/clang/3.5/include/stdarg.h:33:52: note: 
expanded from macro 'va_start'
#define va_start(ap, param) __builtin_va_start(ap, param)
                                                   ^
../../3rdparty/libprocess/3rdparty/stout/include/stout/os.hpp:727:60: note: 
parameter of type 'const std::string &'
      (aka 'const basic_string<char> &') is declared here
inline Try<int> shell(std::ostream* os, const std::string& fmt, ...)

../../3rdparty/libprocess/3rdparty/stout/include/stout/format.hpp:402:18: 
error: 'va_start' has undefined behavior with
      reference types [-Werror,-Wvarargs]
  va_start(args, fmt);
                 ^
/root/clang/build/Release/bin/../lib/clang/3.5/include/stdarg.h:33:52: note: 
expanded from macro 'va_start'
#define va_start(ap, param) __builtin_va_start(ap, param)
                                                   ^
../../3rdparty/libprocess/3rdparty/stout/include/stout/format.hpp:399:51: note: 
parameter of type 'const std::string &'
      (aka 'const basic_string<char> &') is declared here
inline Try<std::string> format(const std::string& fmt, ...)




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to