dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #26022
Re: Slow PetscInitialize?
-
To:
"Garth N. Wells" <gnw20@xxxxxxxxx>
-
From:
Anders Logg <logg@xxxxxxxxx>
-
Date:
Mon, 15 Oct 2012 13:59:39 -0500
-
Cc:
DOLFIN Mailing List <dolfin@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CAA4C66PsOM0qQChN4jVmugEdkCGoJWRkiEyWhBZrweoHe0Ri=g@mail.gmail.com>
-
User-agent:
Mutt/1.5.21 (2010-09-15)
On Mon, Oct 15, 2012 at 05:28:50PM +0100, Garth N. Wells wrote:
> > Do we have that documented somewhere? It would be good to get this
> > into Dorsal (if possible) to make it easy to share the knowledge of
> > how to build 'hpc' versions of FEniCS on some standard systems.
> >
>
> Not documented, but the issue is simple: with dynamically linked
> libraries in standard paths it's mayhem trying figure out what's being
> linked when different libraries link to different library versions of
> the same package..
Could you share some pointers on how you have set up your build, which
versions of packages (MPICH or OpenMPI), which BLAS, version numbers
etc and I can try to replicate and think about whether this can be
documented as part of Dorsal or somewhere else.
> I hope you're not referring to 'standard HPC' systems. They don't exist.
I'm referring to having a good build of the FEniCS software stack on a
standard desktop or laptop running the latest Ubuntu which is what
most of us have. I've been relying on Dorsal which tries to use as
many Debian packages as possible, but apparently that is not enough.
--
Anders
Follow ups
References