Åsmund Ødegård wrote:
> 
> 
> On Nov 30, 2007 6:08 PM, Garth N. Wells <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
> 
>     To get the flags right for MPI, the test in petsc.py should use mpicc
>     (or mpicxx) if PETSc has been compiled using MPI, instead of g++.
> 
> 
> You're right - I haven't tought about that. Unfortunately, pkg-config 
> which we use quite heavily does not really supports the concept of 
> telling about compilers, so I have to find some clever way to deal with 
> this issue :-)
>

We got around this with DOLFIN by doing

   pkg-config --variable=compiler dolfin

Garth


> Thanks for testing!
> 
> 
>     Garth
> 
>     Garth N. Wells wrote:
>      >
>      > Åsmund Ødegård wrote:
>      >>
>      >> On Nov 30, 2007 5:32 PM, Garth N. Wells <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>
>      >> <mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
>      >>
>      >>     [snip]
>      >>      >
>      >>      > Usually, you should set what you used as prefix when
>     installing
>      >>     umfpack.
>      >>      >
>      >>
>      >>     I'm using Ubuntu 7.10 with the libsuitespare-dev package.
>     The header
>      >>     files are located under
>      >>
>      >>       /usr/include/suitesparse
>      >>
>      >>     "suitesparse" needs to be added to
>      >>
>      >>       ./simula-scons/scons/pkgconfiggenerator/umfpack.py
>      >>
>      >>
>      >> Thanks Garth. I thought that was already in there, but obviously it
>      >> wasn't. Added upstream now.
>      >>
>      >
>      > I'm also having a problem with petsc.py. I'm still trying to
>     figure it
>      > out, but it appears to be related to the location of the MPI
>     header files.
>      >
>      > Garth
>      >
>      >
>      >> --
>      >> [simula.research laboratory]
>      >>                 Åsmund Ødegård
>      >>                 IT-Manager
>      >>                 phone: +4790069915
>      >>                 http://www.simula.no/ <http://www.simula.no/>
>      >
>      >
>      > _______________________________________________
>      > DOLFIN-dev mailing list
>      > [email protected] <mailto:[email protected]>
>      > http://www.fenics.org/mailman/listinfo/dolfin-dev
>      >
> 
_______________________________________________
DOLFIN-dev mailing list
[email protected]
http://www.fenics.org/mailman/listinfo/dolfin-dev

Reply via email to