On Tue, 20 Apr 2010, Roy Stogner wrote:
> On Tue, 20 Apr 2010, Kirk, Benjamin (JSC-EG311) wrote:
>
>> I have no problem using the approach where we can, provided we don't
>> blow away the current capability for dealing with makefile-less
>> petsc installations.
>
> I was actually suggesting using $PETSC_SNES_LIB, on the theory that
> that can get snarfed from the same {packages,petscconf,petscvariables}
> file that we're currently including. But it turns out that
> $PETSC_SNES_LIB is not in $PETSC_ARCH/conf/petscvariables, it's in
> conf/variables (or bmake/common/variables), which we don't currently
> include.
This seems to be working on PETSc 3.1, 3.0, and 2.3.3 for me. I'm
going to commit it now to let it get a little wider exposure.
> I'm not sure what else a makefile-less petsc installation
> might have missing.
And I'm still not sure - so everyone feel free to scream at me if you
have trouble building or linking after your next svn update.
---
Roy
------------------------------------------------------------------------------
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
