...
URL:
http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20090506/da2def88/attachment.html
On Tue, 5 May 2009, Giuseppe Ghib? wrote:
Hi.
I'm trying to package petsc 2.3.3,
Why package this older version? Current version is 3.0.0.
but I didn't understand the logic of some options, in particular for
umfpack. E.g. If I specify at the config stage:
...
URL:
http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20090506/cb02dcf2/attachment.html
On Wed, 6 May 2009, Matthew Knepley wrote:
You can force in a library using the full path.
Not with the python-list mode. Here configure automatically converts
[/foo/bar/libfoobar.a] to -L/foo/bar -lfooobar [i.e compiler
automatically picks up shared library - not static]
I think the right
What to you think about also accepting -pc_factor_solver (as a
second chance if the former -pc_factor_mat_solver_package is not
found) ?
--
Lisandro Dalc?n
---
Centro Internacional de M?todos Computacionales en Ingenier?a (CIMEC)
Instituto de Desarrollo Tecnol?gico para la Industria
Currently, -snes_mf* options are handled in SNESSetUp()... I think all
you will agree that the proper place for them is
SNESSetFromOptions()... However, perhaps I'm missing something and
things are like that for some reason... In that case I would like to
know the reason and perhaps I could fix
Lisandro,
The checking of the options can be moved to SNESSetFromOptions()
that then set some flag in the snes object;
but the actual action of MatCreateSNESMF() etc must continue to take
place in the setup.
Feel free to change if you like,
Barry
On May 6, 2009, at
On May 6, 2009, at 3:37 PM, Lisandro Dalcin wrote:
On Wed, May 6, 2009 at 5:25 PM, Barry Smith bsmith at mcs.anl.gov
wrote:
Lisandro,
The checking of the options can be moved to
SNESSetFromOptions() that
then set some flag in the snes object;
but the actual action of
