Hi Folks,
I am trying to test the changes I have made to the PLAPACKR32-hg package
before pushing them back up and asking Satish to rebuild the tarball. I
guessed that I could do this by deleting
$PETSC_DIR/externalpackages/PLAPACKR32-hg and
$PETSC_DIR/$PETSC_ARCH/lib/libPLAPACK.a, pointing
On Mon, 7 Nov 2011, Richard Tran Mills wrote:
Hi Folks,
I am trying to test the changes I have made to the PLAPACKR32-hg package
before pushing them back up and asking Satish to rebuild the tarball. I
guessed that I could do this by deleting
$PETSC_DIR/externalpackages/PLAPACKR32-hg and
Hi Satish,
Thanks very much for your help with my dumb BuildSystem question.
I have tested my changes to PLAPACKR32-hg and pushed my changeset back to the
repo. (I just fixed some missing function prototypes, one of which was
causing problems on 64-bit systems for me.) Can you please update
tarball is updated now.
Satish
On Mon, 7 Nov 2011, Richard Tran Mills wrote:
Hi Satish,
Thanks very much for your help with my dumb BuildSystem question.
I have tested my changes to PLAPACKR32-hg and pushed my changeset back to the
repo. (I just fixed some missing function prototypes
Hi!
I am unclear about where external packages required by PETSc should
go. Many packages (like PETSc, TAO, OOQP) might want to use some common
external package (like MPICH). But it seems like a wasted effort if we
replicate the PETSc build scripts which already install these packages
into
Hi!
Ideally, I would like to use your BuildSystem to hack up a quick build
for Numerix. Then as we add and integrate more tools in, I would work on
making it fancier.
Matt Cool, we can do that.
Step one in that direction would be for me to adapt make.py in
$PETSC_DIR to build our shared
S V N Vishwanathan vishy at mail.rsise.anu.edu.au writes:
Ideally, I would like to use your BuildSystem to hack up a quick build
for Numerix. Then as we add and integrate more tools in, I would work on
making it fancier.
Cool, we can do that.
Here is the plan I came up with (after
Hi!
I am tying myself up in knots in trying to figure out your BuildSystem
and how to adapt it to LINEAL. PETSc is one primary component of LINEAL
but going forward there will be others (viz. TAO, OOQP).
I want that my users should be exposed to one and only one config + make
step if possible.
S V N Vishwanathan vishy at mail.rsise.anu.edu.au writes:
Hi!
I am tying myself up in knots in trying to figure out your BuildSystem
and how to adapt it to LINEAL. PETSc is one primary component of LINEAL
but going forward there will be others (viz. TAO, OOQP).
I want that my users should
