Looks like this change broke my build. download-mpi looks
ambigeous. If added - perhaps it should be an alias to download-mpich.
Satish
asterix:/home/balay/tmp/spetsc./configure
--with-mpi-dir=/home/balay/soft/linux64/mpich2-1.1
I suggest we can the syntax for 2) and consistently use --known-
mpi-shared --known-sizeofint=8 etc everywhere in help and BuildSystem.
It makes things much clearer and can prevent loads of confusion.
This is likely not compatible with how autoconf does things. Do
they have a similar
Would you not consider using a perfectly decent autoconf-like
construct
such as, in the MPI case,
--with-known-mpi-shared
given that it is with the knowledge of the shared MPI that you are
building ?
We could do this. It is a bit wordy with the --with however, if it
is always
I think a root of the miscommunication between Matt and I with
regard to --with-mpi-shared is that --with is used for TWO different
reasons
1) --with-mpi=0 --with-x=1 etc are used to indicate we want to turn
off/on a package. In other words they are COMMANDS to BuildSystem
2)
--with-mpi=0 is a command, which is mandatory, and --with-sizeofint=8
seems to specify an optional parameter.
To me '--with' suggests something optional, so I'd vote for keeping
'--with' to indicate
optional parameters and replace it with '--use' (an imperative) when
specifying mandatory commands.
Wrt batch mode, the relavent PETSc configure flags are:
'--with-batch=1',
'--with-mpi-shared=0',
'--with-memcmp-ok',
'--sizeof_char=1',
'--sizeof_void_p=4',
'--sizeof_short=2',
'--sizeof_int=4',
'--sizeof_long=4',
'--sizeof_size_t=4',
'--sizeof_long_long=8',
It should be pay off to be consistent :-(. I have see a --have in
there :-)
Barry
On Dec 15, 2009, at 3:30 PM, Satish Balay wrote:
Wrt batch mode, the relavent PETSc configure flags are:
'--with-batch=1',
'--with-mpi-shared=0',
'--with-memcmp-ok',
'--sizeof_char=1',
