https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199601
--- Comment #76 from Don Lewis <[email protected]> --- (In reply to Raphael Kubo da Costa from comment #75) > I'm waiting for replies to my comment in bug 207600. Please keep kde@ in the > loop for changes in akonadi. It appears possible to patch boost so that akonadi builds without any further changes. --- boost/config/compiler/clang.hpp.orig 2015-12-08 18:55:19 UTC +++ boost/config/compiler/clang.hpp @@ -167,7 +167,7 @@ # define BOOST_NO_CXX11_UNIFIED_INITIALIZATION_SYNTAX #endif -#if !__has_feature(cxx_rvalue_references) +#if !__has_feature(cxx_rvalue_references) || (defined(__GLIBCXX__) && __GLIBCXX__ < 20080606) # define BOOST_NO_CXX11_RVALUE_REFERENCES #endif devel/liborcus runs into the same problem, but the above patch is not sufficient. It relies on one of a number of c++ headers having already been included in order to bring in <bits/c++config.h> so that __GLIBCXX__ gets defined. The liborcus source is OK, but configure has a problem and thinks that <boost/filesystem/path.hpp> is not usable. The following ugly patch to configure fixes that: --- configure.orig 2015-06-18 23:43:37 UTC +++ configure @@ -18668,7 +18668,8 @@ ac_link='$CXX -o conftest$ac_exeext $CXX ac_compiler_gnu=$ac_cv_cxx_compiler_gnu boost_save_CPPFLAGS=$CPPFLAGS CPPFLAGS="$CPPFLAGS $BOOST_CPPFLAGS" -ac_fn_cxx_check_header_mongrel "$LINENO" "boost/filesystem/path.hpp" "ac_cv_header_boost_filesystem_path_hpp" "$ac_includes_default" +ac_fn_cxx_check_header_mongrel "$LINENO" "boost/filesystem/path.hpp" "ac_cv_header_boost_filesystem_path_hpp" "$ac_includes_default +#include <ios>" if test "x$ac_cv_header_boost_filesystem_path_hpp" = xyes; then : $as_echo "#define HAVE_BOOST_FILESYSTEM_PATH_HPP 1" >>confdefs.h @@ -18720,6 +18721,7 @@ else # Generate the test file. cat confdefs.h - <<_ACEOF >conftest.$ac_ext /* end confdefs.h. */ +#include <ios> #include <boost/filesystem/path.hpp> int Does this look like a reasonable direction to take? -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ kde-freebsd mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
