Re: [Libmesh-devel] PETSc has no $PETSC_ARCH directory component when installed.

2010-12-01 Thread Roy Stogner
Thanks very much, and sorry I let this get buried in my outbox - it's in the svn head now. --- Roy On Tue, 9 Nov 2010, Erik Zeek wrote: > When PETSc is installed into a prefix directory it no longer has a directory > component for $PETSC_ARCH. The test for PETSc MPI support didn't allow for > t

Re: [Libmesh-devel] PETSc has no $PETSC_ARCH directory component when installed.

2010-11-09 Thread Barry Smith
On Nov 9, 2010, at 4:35 PM, Cody Permann wrote: > There are other issues with using prefix installs of PETSc. It turns out > that there are links back to the source directory where you build PETSc for > any external libraries you use. At least this is the case with the newest > version of PE

Re: [Libmesh-devel] PETSc has no $PETSC_ARCH directory component when installed.

2010-11-09 Thread Cody Permann
There are other issues with using prefix installs of PETSc. It turns out that there are links back to the source directory where you build PETSc for any external libraries you use. At least this is the case with the newest version of PETSc 2.X. You will see this if you delete the source direc

[Libmesh-devel] PETSc has no $PETSC_ARCH directory component when installed.

2010-11-09 Thread Erik Zeek
When PETSc is installed into a prefix directory it no longer has a directory component for $PETSC_ARCH. The test for PETSc MPI support didn't allow for this case. The attached patch allows for this, but doesn't allow $PETSC_ARCH to be unset. Erik P.S. The other workaround I found was to set