[
https://issues.apache.org/jira/browse/MESOS-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848494#comment-13848494
]
Till Toenshoff commented on MESOS-860:
--------------------------------------
I do entirely understand the need for getting rid of bundled and possibly even
patched dependencies.
How about this, for now, to make sure that developers don't hit the wall when
compiling but already when configuring? We could add a couple of autoconf
checks that increase the chances of a success when building.
For this specific dependency, it would be checking of ext/slist was available;
# Check for ext/slist as glog 0.3.3 relies on that SGI extension
# to the standard C++ library.
# TODO(tillt): Remove this when glog has a resolution.
AC_LANG_PUSH([C++])
AC_CHECK_HEADER([ext/slist], [],
[AC_MSG_ERROR([can not find ext/slist
-------------------------------------------------------------------
We need ext/slist for glog.
-------------------------------------------------------------------])], [])
AC_LANG_POP([C++])
> Get mesos' libprocess dependency glog to compile with clang and libc++
> ----------------------------------------------------------------------
>
> Key: MESOS-860
> URL: https://issues.apache.org/jira/browse/MESOS-860
> Project: Mesos
> Issue Type: Improvement
> Components: build, libprocess
> Affects Versions: 0.14.2
> Environment: OS X 10.9 (Mavericks), Apple LLVM version 5.0
> (clang-500.2.79) (based on LLVM 3.3svn)
> Reporter: Till Toenshoff
> Priority: Minor
> Labels: build, glog, libprocess, patch
> Attachments: glog-0.3.3-R139-libc++.tar.gz, glog-upgrade.diff
>
>
> [mesos/build/3rdparty/libprocess/3rdparty/glog-0.3.3(master) ]
> Failure:
> In file included from src/stl_logging_unittest.cc:34:
> ./src/glog/stl_logging.h:56:11: fatal error: 'ext/slist' file not found
> # include <ext/slist>
> ^
> 2 warnings and 1 error generated.
> make[7]: *** [stl_logging_unittest-stl_logging_unittest.o] Error 1
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
