Dear Ziji, the log output doesnt contain the actual error message. Can you please make sure Nektar is compiled with -DCMAKE_BUILD_TYPE=debug, run ctest with the "--output-on-failure" option and post the content of one of the .err and .out files it creates? Cheers, Kilian Am 06.06.2018 um 17:42 schrieb #SHI ZIJI#:
Dear all, I am trying to build Nektar++4.4.1 with third party PETSc and Arpack. The third party version of PETSc compiles, but it failed all of the tests. I executed the test command and it returned seg fault (seg fault for first 4 tests and exception for the rest). However, if I removed NEKTAR_USE_PETSC and THIRDPARTY_BUILD_PETSC, the tests can be passed.
The command I used looks like the following:
CC=mpiicc CXX=mpiicpc FC=mpiifort cmake\ -DNEKTAR_USE_MKL=ON \ -DNEKTAR_USE_PETSC=ON \ -DNEKTAR_USE_MPI=ON \ -DTHIRDPARTY_BUILD_PETSC=ON ..
The test log is attached in this email.
Meanwhile, may I know if Arpack can be supported with third party build? The cmake/ThirdPartyArpack.cmake is more like a FindArpack.cmake script.
Many thanks in advance!
Best Regards, Ziji
_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users
-- Kilian Lackhove, M.Sc. Fachgebiet für Energie- und Kraftwerkstechnik L1|08 114 Technische Universität Darmstadt Otto-Berndt-Straße 3 D-64287 Darmstadt Germany Tel.: +49 6151 16 - 28915 Fax: +49 6151 16 - 6555 e-mail: lackhove@ekt.tu-darmstadt.de