Alex,
I am glad it is finally working. To answer your question, when using
Trilinos MPI is required. We just merged a fix that makes this clear:
https://github.com/dealii/dealii/pull/12381
Best,
Bruno
Le mer. 9 juin 2021 à 11:18, Alex Cumberworth
<alexandercumberwo...@gmail.com> a écrit :
>
> Hello,
>
> I finally managed to get everything compiled and running. To solve the last
> issue, I started completely fresh with trilinos, and it no longer tried to
> find the static version of sacado. I think there must have been something
> leftover in the cmake files in the installation of trilinos from a previous
> build without the build shared libraries option in trilinos configuration.
>
> To summarize the more generalizable issues from this:
>
> - If there are issues when including trilinos in the build, consider
> compiling trilinos with MPI to ensure it will have the same MPI version as
> deal.ii
> - If there are weird MPI issues with not finding header files, make sure that
> MPI was set on the first call of cmake (as I think one thing that happened
> here was I changed it later and the compiler did not get updated to the
> proper mpi wrapper, or at least I noticed this when compiling trilinos)
> - If you are running on a cluster system with loadable modules, make sure
> things are properly loaded (and or unloaded) before running cmake. This could
> be especially relevant when there are multiple MPI implementations present
> - Check whether the cmake variables are what you think they are (e.g., check
> uppercase vs lower case)
>
> I never did get deal.ii to compile when including tpetra, but since I didn't
> need it I didn't attempt again with the other issues solved, so I can't say
> too much more about that.
>
> One thing that is still unclear to me: is it possible to compile trilinos and
> deal.ii without MPI? It seemed here that there are wrapper classes that
> trilinos will only compile if MPI is enabled? If this is true, perhaps that
> should be included on this this page?
>
> Thanks to everyone that helped!
>
> Best,
> Alex
>
> On Tuesday, June 8, 2021 at 6:37:09 a.m. UTC+2 vachanpo...@gmail.com wrote:
>>
>> Alex,
>>
>> I think this is a problem related to the cluster's OS. On Cray XC50, I had
>> to explicitly set the link type to dynamic before installation, because by
>> default Cray does a static link. I had to set
>>
>> export XTPE_LINK_TYPE=dynamic
>> export CRAYPE_LINK_TYPE=dynamic
>>
>> before the installation. You can try and see if anything similar is
>> happening.
>>
>> Regards,
>> Vachan
>>
>> On Mon, 7 Jun 2021 at 22:34, Wolfgang Bangerth <bang...@colostate.edu> wrote:
>>>
>>> On 6/7/21 10:35 AM, Alex Cumberworth wrote:
>>> >
>>> > make[2]: *** No rule to make target
>>> > '/home/ipausers/cumberworth/lib/libsacado.a', needed by
>>> > 'lib/libdeal_II.g.so.9.3.0'. Stop.
>>> > make[1]: *** [CMakeFiles/Makefile2:3238:
>>> > source/CMakeFiles/deal_II.g.dir/all]
>>> > Error 2
>>> > make: *** [Makefile:149: all] Error 2
>>> >
>>> > There is libsacado.so in the directory I specified for trilinos
>>> > libraries. I
>>> > configured both trilinos and deal.ii to build shared libraries. I also
>>> > have set
>>> >
>>> > DEAL_II_PREFER_STATIC_LIBS OFF
>>> >
>>> > I'm not really sure why it seems to only look for the static version of
>>> > the
>>> > library.
>>>
>>> I don't think that the deal.II configuration specifies this. Check the files
>>> under lib/cmake in your Trilinos installation. For example, I find there the
>>> following information that deal.II simply imports:
>>>
>>> trilinos-12.8.1-mpi/lib> grep -r libsacado *
>>> cmake/Sacado/SacadoTargets-release.cmake: IMPORTED_LOCATION_RELEASE
>>> "${_IMPORT_PREFIX}/lib/libsacado.so.12.8.1"
>>> cmake/Sacado/SacadoTargets-release.cmake: IMPORTED_SONAME_RELEASE
>>> "libsacado.so.12"
>>> cmake/Sacado/SacadoTargets-release.cmake:list(APPEND
>>> _IMPORT_CHECK_FILES_FOR_sacado "${_IMPORT_PREFIX}/lib/libsacado.so.12.8.1" )
>>> Binary file libsacado.so matches
>>> Binary file libsacado.so.12 matches
>>> Binary file libsacado.so.12.8.1 matches
>>>
>>> Best
>>> W.
>>>
>>> --
>>> ------------------------------------------------------------------------
>>> Wolfgang Bangerth email: bang...@colostate.edu
>>> www: http://www.math.colostate.edu/~bangerth/
>>>
>>> --
>>> 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 dealii+un...@googlegroups.com.
>>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dealii/59c24df0-17d6-5c39-4ef9-9ba5fb722ca8%40colostate.edu.
>
> --
> 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 a topic in the Google
> Groups "deal.II User Group" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dealii/3_Tr8HLd7UM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> dealii+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dealii/97775ce8-94cd-4a78-ac3c-804cdd5aa74cn%40googlegroups.com.
--
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 dealii+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/dealii/CAGVt9eNM%2BPZpN9DvL6kfN36ggkcP2VsdOiXxXcUc1vgwjJYPRA%40mail.gmail.com.
