Dear all, After discussion with my cluster admin, he suggested the use of the following flag:
-DTrilinos_FIND_COMPONENTS="Pike;PikeImplicit;PikeBlackBox;TrilinosCouplings;Panzer;PanzerMiniEM;PanzerAdaptersSTK;PanzerDiscFE;PanzerDofMgr;PanzerCore;Piro;ROL;Stokhos;Tempus;Rythmos;ShyLU;ShyLU_DD;ShyLU_DDCommon;ShyLU_DDFROSch;ShyLU_DDBDDC;Zoltan2;Zoltan2Sphynx;MueLu;Moertel;NOX;Phalanx;Percept;STK;STKExprEval;STKDoc_tests;STKUnit_tests;STKBalance;STKTools;STKTransfer;STKSearchUtil;STKSearch;STKUnit_test_utils;STKNGP_TEST;STKIO;STKMesh;STKTopology;STKSimd;STKUtil;STKMath;Compadre;Intrepid2;Intrepid;Teko;FEI;Stratimikos;Ifpack2;Anasazi;Komplex;SEACAS;SEACASEx2ex1v2;SEACASTxtexo;SEACASNumbers;SEACASNemspread;SEACASNemslice;SEACASMat2exo;SEACASMapvar-kd;SEACASMapvar;SEACASMapvarlib;SEACASExplore;SEACASGrepos;SEACASGenshell;SEACASGen3D;SEACASGjoin;SEACASFastq;SEACASEx1ex2v2;SEACASExo_format;SEACASExotxt;SEACASExomatlab;SEACASExodiff;SEACASExo2mat;SEACASEpu;SEACASEjoin;SEACASConjoin;SEACASBlot;SEACASAprepro;SEACASAlgebra;SEACASPLT;SEACASSVDI;SEACASSuplibCpp;SEACASSuplibC;SEACASSuplib;SEACASSupes;SEACASAprepro_lib;SEACASChaco;SEACASIoss;SEACASNemesis;SEACASExoIIv2for32;SEACASExodus_for;SEACASExodus;Amesos2;ShyLU_Node;ShyLU_NodeTacho;ShyLU_NodeHTS;Belos;ML;Ifpack;Zoltan2Core;Pamgen;Amesos;Galeri;AztecOO;Pliris;Isorropia;Xpetra;Thyra;ThyraTpetraAdapters;ThyraEpetraExtAdapters;ThyraEpetraAdapters;ThyraCore;Domi;TrilinosSS;Tpetra;TpetraCore;TpetraTSQR;TpetraClassic;EpetraExt;Triutils;Shards;Zoltan;Epetra;MiniTensor;Sacado;RTOp;KokkosKernels;Teuchos;TeuchosKokkosComm;TeuchosKokkosCompat;TeuchosRemainder;TeuchosNumerics;TeuchosComm;TeuchosParameterList;TeuchosParser;TeuchosCore;Kokkos;KokkosAlgorithms;KokkosContainers;KokkosCore;Gtest;TrilinosATDMConfigTests;TrilinosFrameworkTests" I guess this enables us to choose which Trilinos components we include and which we don't. Interesting to say the least, I will have to test more to see if this has consequences. Thank you for your help and your time. This is always greatly appreciated. I hope this may help others in the future. Best Bruno On Friday, October 29, 2021 at 10:01:15 a.m. UTC-4 bruno.t...@gmail.com wrote: > Bruno, > > It looks like you are not the only one to have this problem: > https://github.com/trilinos/Trilinos/issues/8299 > https://github.com/trilinos/Trilinos/issues/9426 > > Possible solution from the second issue: use `-DBUILD_SHARED_LIBS:BOOL=OFF` > or add -undefined dynamic_lookup to CMAKE_CXX_FLAGS > > Best, > > Bruno > On Friday, October 29, 2021 at 9:41:01 AM UTC-4 Wolfgang Bangerth wrote: > >> On 10/29/21 7:10 AM, blais...@gmail.com wrote: >> > Is there a way to disable the usage of Zadelus from deal.II? >> > I don't see any CMAKE options that I could pass to disable Zadelus. >> > I tried googling the component and I can't figure out what it is... >> > :) >> > I'll ask my cluster administrator to recompile Trilinos with Zadelus, I >> just >> > hope it's not an old component that was deprecated in Trilinos 13.0.1 >> >> I think you will have to recompile Trilinos without that specific >> package. >> When you compile Trilinos, you pass a list of cmake flags of the form >> TPL_ENABLE_... for the package you want, and you probably want to omit >> (or >> explicitly disable) the one that is the problem. >> >> 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dealii/b2cffa25-73ac-4b7b-b7ba-bed99b9aa9c3n%40googlegroups.com.
