On Fri, 12 Dec 2008, Jose E. Roman wrote:
SLEPc's configure.py uses the value of $PETSC_ARCH in order to setup
everything for installation. We never had a $SLEPC_ARCH variable because our
configure.py does not add platform-dependent functionality.
Now the problem comes when PETSc has been
SLEPc's configure.py uses the value of $PETSC_ARCH in order to setup
everything for installation. We never had a $SLEPC_ARCH variable
because our configure.py does not add platform-dependent functionality.
Now the problem comes when PETSc has been configured with --prefix and
installed with
I would like to add that, despite the new buildsystem if by far better
than the old one, PETSc has lost a nice feature of being able of being
installed in a central location for multiple $PETSC_ARCH's . This
feature is something I need, as I have to maintain the PETSc
intallation in our cluster,
I need to understand what you use this variable for. If you are just
linking, then you
do not need it. If you want configure information, then you need it in order
to get
anything, so specifying in a file will not help.
Matt
On Fri, Dec 12, 2008 at 9:01 AM, Jose E. Roman jroman at dsic.upv.es
On Fri, Dec 12, 2008 at 9:32 AM, Lisandro Dalcin dalcinl at gmail.com wrote:
I would like to add that, despite the new buildsystem if by far better
than the old one, PETSc has lost a nice feature of being able of being
installed in a central location for multiple $PETSC_ARCH's . This
feature
On Fri, 12 Dec 2008, Satish Balay wrote:
A simple workaround would be that PETSc's configure (or make install) would
add a variable (e.g. PETSC_ARCH_NAME) in file petscvariables. We parse this
file so the arch name would be readily available even if $PETSC_ARCH is
undefined.
Currently
On Fri, 12 Dec 2008, Satish Balay wrote:
On Fri, 12 Dec 2008, Lisandro Dalcin wrote:
I would like to add that, despite the new buildsystem if by far better
than the old one, PETSc has lost a nice feature of being able of being
installed in a central location for multiple $PETSC_ARCH's .
On 12/12/2008, Jose E. Roman wrote:
SLEPc's configure.py uses the value of $PETSC_ARCH in order to setup
everything for installation. We never had a $SLEPC_ARCH variable
because our configure.py does not add platform-dependent
functionality.
Now the problem comes when PETSc has been
If PETSC_ARCH is not set, I would just use the default arch generated by
configure, like
we do in the PETSc configure.
Matt
On Fri, Dec 12, 2008 at 11:29 AM, Jose E. Roman jroman at dsic.upv.es wrote:
On 12/12/2008, Jose E. Roman wrote:
SLEPc's configure.py uses the value of $PETSC_ARCH
