Lisandro,
That change will certainly NOT be reverted. PETSC_ARCH_NAME!
what the heck kind of variable name is that?
I need to understand the reason for PETSC_ARCH_NAME, then we can
come up with some solution. What is the difference between
PETSC_ARCH_NAME and PETSC_ARCH? Is it only needed when --prefix is
used (so PETSC_ARCH does not exist), if so, exactly why is it needed,
the whole idea behind --prefix is to eliminate PETSC_ARCH, so why is
it needed? How is PETSC_ARCH_NAME used?
Barry
On Nov 25, 2009, at 10:14 AM, Lisandro Dalcin wrote:
> Barry, an outcome of the two changesets below:
>
> changeset: 14451:b289577caf8f
> user: barrysmith at bsmith-laptop.mcs.anl.gov
> date: Mon Oct 19 16:31:16 2009 -0500
> summary: update to install.py to ONLY use RDict.db (and not
> command line)
>
> changeset: 14383:447d34bd2d4b
> user: barrysmith at bsmith-laptop.mcs.anl.gov
> date: Thu Oct 08 16:33:59 2009 -0500
> summary: finished cleaning up makefiles, moved charactoristic.h to
> include location standard place where it is easy to use
>
>
> was that these two lines in config/PETSc/utilities/arch.py were
> removed:
>
> # SLEPc configure need this info
> self.addMakeMacro('PETSC_ARCH_NAME',self.arch)
>
>
> SLEPc and petsc4py/slepc4py/tao4py relies on this variable being
> defined in makefiles. There is now a new way to get the original name
> of the build-time $PETSC_ARCH? If not, any chance this change could be
> reverted?
>
> --
> Lisandro Dalc?n
> ---------------
> Centro Internacional de M?todos Computacionales en Ingenier?a (CIMEC)
> Instituto de Desarrollo Tecnol?gico para la Industria Qu?mica (INTEC)
> Consejo Nacional de Investigaciones Cient?ficas y T?cnicas (CONICET)
> PTLC - G?emes 3450, (3000) Santa Fe, Argentina
> Tel/Fax: +54-(0)342-451.1594
