[EMAIL PROTECTED] wrote: > On Mon, Mar 17, 2008 Johannes Ring wrote: >> On Mon, Mar 17, 2008 Garth N. Wells wrote: >>> >>> [EMAIL PROTECTED] wrote: >>>> On Mon, Mar 17, 2008 Garth N. Wells wrote: >>>>> On a side note, when compiling with PETSc, g++ is being used instead >>>>> of >>>>> mpicxx. Shouldn't it be mpicxx if that's what PETsc used? >>>> Yes, it should use the compiler that PETSc was compiled with. What does >>>> the petsc.pc file say? What does 'pkg-config dolfin >>>> --variable=compiler' >>>> say? >>>> >>> petsc.pc says mpicxx >>> >>> dolfin.pc says g++, and 'pkg-config dolfin --variable=compiler' returns >>> 'g++' >> I'm sorry, I meant 'pkg-config petsc --variable=compiler'. It should of >> course return 'mpicxx'.
Yes, it does. Garth >> >>> I do get the below output from scons. >>> >>> Garth >>> >>> Trying to generate pkg-config file for petsc... Does not know about >>> any alternates for mpicxx, so that is used >>> Does not know about any alternates for mpicxx, so that is used >>> Does not know about any alternates for mpicxx, so that is used >>> Does not know about any alternates for mpicxx, so that is used >>> Does not know about any alternates for mpicxx, so that is used >>> Does not know about any alternates for mpicxx, so that is used >>> Does not know about any alternates for mpicxx, so that is used >>> Does not know about any alternates for mpicxx, so that is used >>> done >> Strange. Need to look into that. > > I think this is okay in this case. The output should be changed though. > > Johannes > > > _______________________________________________ > DOLFIN-dev mailing list > [email protected] > http://www.fenics.org/mailman/listinfo/dolfin-dev _______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
