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,
Wiener
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20081212/24ec32b2/attachment.html
://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20081212/2187efb8/attachment.html
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
-dev/attachments/20081212/8a2b3210/attachment.html
When using petsc-2.3.3+tao-1.9, TAO does require that PETSc be built
with C++. I believe this is just because a PETSc built with C cannot
always provide enough info to TAO makefiles about the C++ compiler...
However, when PETSc is built with a external that requires C++/mpicxx,
then it seems some
On Dec 12, 2008, at 1:50 PM, Lisandro Dalcin wrote:
When using petsc-2.3.3+tao-1.9, TAO does require that PETSc be built
with C++. I believe this is just because a PETSc built with C cannot
always provide enough info to TAO makefiles about the C++ compiler...
However, when PETSc is built
We are eventually moving TAO away from the C++ necessity, probably for
next release (after a PETSc-3 compatibile release). I agree with
Barry that now is not the time to start changing PETSc configure.
Jason
On Fri, 12 Dec 2008, Barry Smith wrote:
On Dec 12, 2008, at 1:50 PM, Lisandro
Hello,
I can see from the recent flurry of activity that many people are working
very diligently to get the next release of PETSc out of the door in the
near future, and I will soon be installing this new release on several
large unclassified machines at several DoD centers, and I am also
Tom,
The changes file is currently at
http://www.mcs.anl.gov/petsc/petsc-as/documentation/changes/dev.html
after the release it will be at
http://www.mcs.anl.gov/petsc/petsc-as/documentation/changes/300.html
Barry
On Dec 12, 2008, at 2:57 PM, Tom Cortese wrote:
Hello,
I can
Great -- thanks!
-Tom C.
On Fri, 12 Dec 2008, Barry Smith wrote:
Tom,
The changes file is currently at
http://www.mcs.anl.gov/petsc/petsc-as/documentation/changes/dev.html
after the release it will be at
http://www.mcs.anl.gov/petsc/petsc-as/documentation/changes/300.html
15 matches
Mail list logo
