Update: Boost-1.66 is (currently) not that compatible to CMake, thus it is 
not related to deal.II

Am Dienstag, 9. Januar 2018 13:48:37 UTC+1 schrieb Maxi Miller:
>
> I know that there already a similar bug report exists for the combination 
> of deal.II and cmake 3.10 (i.e. MPI is not working). Unfortunately I can 
> not downgrade CMake, thus I have to work with this version. I implemented 
> the pull request https://github.com/dealii/dealii/pull/5690 in my local 
> version, but it still fails with the same error (using OpenMPI and GCC 
> 7.2). Is there anything else I can do?
> Furthermore I get a lot of errors like
>
> CMake Warning at /usr/share/cmake/Modules/FindBoost.cmake:801 (message):
> New Boost version may have incorrect or missing dependencies and imported
> targets
> Call Stack (most recent call first):
> /usr/share/cmake/Modules/FindBoost.cmake:907 
> (_Boost_COMPONENT_DEPENDENCIES)
> /usr/share/cmake/Modules/FindBoost.cmake:1542 (_Boost_MISSING_DEPENDENCIES)
> cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
> cmake/modules/FindBOOST.cmake:50 (FIND_PACKAGE)
> cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
> cmake/configure/configure_boost.cmake:88 (FIND_PACKAGE)
> build/CMakeFiles/CMakeTmp/evaluate_expression.tmp:1 
> (FEATURE_BOOST_FIND_EXTERNAL)
> cmake/macros/macro_evaluate_expression.cmake:30 (INCLUDE)
> cmake/macros/macro_configure_feature.cmake:237 (EVALUATE_EXPRESSION)
> cmake/configure/configure_boost.cmake:201 (CONFIGURE_FEATURE)
> cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
> CMakeLists.txt:124 (VERBOSE_INCLUDE)
>
> since upgrading boost to version 1.66 (from 1.63)
>
> Is that a problem related to deal.II, or to the new CMake-version?
>

-- 
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see 
https://groups.google.com/d/forum/dealii?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to