Skip to content
Snippets Groups Projects

restoring macOS compatibility

Closed Boman Romain requested to merge macOS into master

The code can be compiled with clang on macOS. TABs in FindTBB.cmake have been cleaned.

Some tests of mirrors generate segfaults (on macOS).

44/67 Test #47: mirrors/tests/mparams/loop6.py ............***Exception: SegFault109.68 sec 56/67 Test #53: mirrors/tests/mparams/mparams.py ..........***Exception: SegFault 22.62 sec 65/67 Test #43: mirrors/tests/mparams/loop2.py ............***Exception: SegFault308.35 sec

Other failures should be investigated further:

12/67 Test #12: flow/tests/channel.py .....................***Failed 1.75 sec (problem with my installation of MUMPS on my mac? - works well on Ubuntu) 33/67 Test #27: heat/tests/fe2/heat_mpi.py ................***Failed 9.75 sec

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • ok bonne idée, on peut merger une autre pull request avant (celui de la batterie); ca fera un exercice github

  • Created by: kliegeois

    What should we do with this PR? Was it included in the last PR that you have submitted @rboman ?

  • J'ai voulu tester mais mon mac est éteint. En plus, je dois recompiler mumps pour relancer la batterie. Est ce que trilinos marche sur mac/clang? Si oui, je le compilerai avant de merger.

  • Created by: kliegeois

    Yes, Trilinos works on mac with clang providing that you have installed OpenMP for your compiler or that your compiler supports it.

  • Created by: maartenarnst

    I've added a page to the wiki with a writeup of an installation of Trilinos on MacOS Mojave.

  • thanks @maartenarnst I'll follow your note

  • This pull request is too old. Moreover the mac build is now completely broken "thanks to" :poop:Mojave:poop: upgrade...

    Thus I need to upgrade cmake, mkl, etc. then I need to understand exactly what has changed in the "new" dylib loading mechanism.

Please register or sign in to reply
Loading