Request related to SLEPc
Jose E. Roman
jroman at dsic.upv.es
Fri Dec 12 11:29:01 CST 2008
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 configured with --prefix
> and installed with make install. In that case, $PETSC_ARCH is no
> longer available and SLEPc's configure.py is in trouble.
>
> 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.
>
> Can someone do this? Other solutions are welcome.
>
> Thanks,
> Jose
>
Let me explain the situation a bit better.
In SLEPc's configure.py we now (in slepc-dev) create a directory
called $PETSC_ARCH in $SLEPC_DIR, then $PETSC_ARCH/lib contains the
compiled SLEPc libraries and $PETSC_ARCH/conf contains log files and a
"slepcvariables" file. After building, we allow 'make install' if a --
prefix was specified in SLEPc's configure.py (this is not working in
slepc-dev yet).
The thing is that if $PETSC_ARCH is not set, then we cannot create the
$PETSC_ARCH directory. I guess it would be ok to create the files in
the root $SLEPC_DIR directory, but this may be confusing for users if
they expect a $PETSC_ARCH directory, and more complicated for our
makefiles.
Any suggestion?
The latest SLEPc snapshot is here: http://www.grycap.upv.es/slepc/download/distrib/pre/slepc-dev-081210.tgz
Jose
More information about the petsc-dev
mailing list