Why did you removed PETSC_ARCH_NAME variable in makefiles?

Satish Balay balay at mcs.anl.gov
Fri Nov 27 17:52:33 CST 2009


On Fri, 27 Nov 2009, Satish Balay wrote:

> On Fri, 27 Nov 2009, Barry Smith wrote:
> 
> 
> >    How does the gnu/autoconf world handle this. If you have two gnu/autoconf
> > installed packages how can you tell they are compatible? You should use the
> > same type of mechanism they use.  (what?, they don't have such a mechanism?
> > Well then that is a limitation of the --prefix model and you have to live with
> > that).
> 
> The issue is not what the prefix model dictates. The issue is: do
> slepc/petsc4py support both modes of install similar to PETSc. If not
> why does PETSc need PETSC_ARCH for a prefix install? [if we are so
> pure with supporting gnu/autoconf model?].

I read the comment slightly out of context - please ignore.. [now I
see you are refering to the "unique-identifier" as a sanity check
issue]

satish



More information about the petsc-dev mailing list