configure options

Boyana Norris norris at
Tue Apr 19 14:10:16 CDT 2005


Thanks, this is sufficient for most cases (the only exception I can think of 
is when configure crashed or was interrupted before this file was created, 
which has happened to me a few times).


Satish Balay wrote:
> On Tue, 19 Apr 2005, Boyana Norris wrote:
>>This is a suggestion for a trivial addition to what goes in configure.log
>>(that is, if it's not already available elsewhere). One feature that I've
>>found very handy in the otherwise unpleasant use of gnu configure is the
>>ability to cut and paste the options given to configure from the config.log
>>(or .status) file, in the case when building multiple versions or slightly
>>differently configured builds. This doesn't seem to be available with PETSc's
>>configure, or at least not obviously so. If I take the array of options from
>>configure.log, I can't just paste it on the configure command line.
> Currently this functionality is available as
> bmake/${PETSC_ARCH}/
> It gets created when configure is run. It can be run again with
> additional options.  Changing/removing options would mean editing the
> python syntax.
> Satish

"Everything should be made as simple as possible, but not one bit simpler." 
  Albert Einstein (1879 - 1955) (attributed)

More information about the petsc-dev mailing list