dorsal team mailing list archive

[Harish Narayanan <harish.mlists@xxxxxxxxx>]

On 8/26/10 3:42 PM, Andre Massing wrote:
> 
> I have already tried out building dolfin with dorsal, petsc (including mumps, hypre etc., not petsccore) and openmpi from the macports
> and it went through. The only principal obstacle I encountered was the fact that macports installs the compilerwrappers with an "open" prefix,
> resulting into openmpic++, openmpif90 etc. So I did a dirty symlink trick, which we probably want to avoid. So is there a way telling the name of the
> preferred compilerwrappers , via environment variables or such like to the new shiny cmake buildsystem?

My concerns from a previous e-mail still remain. What do you get when
you do openmpicxx --version? I get the following

i686-apple-darwin10-g++-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5664)
Copyright (C) 2007 Free Software Foundation, Inc.
...

And when I do openmpif90 --version, I get:

GNU Fortran (GCC) 4.4.4
Copyright (C) 2010 Free Software Foundation, Inc.

I am not sure it is a great idea to build something like petsc and use
two different gccs to do it.

Harish