Re: LAM configure changes

From: Paul H. Hargrove (
Date: Thu Oct 31 2002 - 09:36:38 PST

Is the --with-checkpoint option still required?

With regard to  --with-cr-file-dir=DIR, I'd like to say that I think 
that compile time is not the right time to specify the ONLY location for 
checkpoint files (though the last-ditch default could be set at compile 

I think that the location of the checkkpoint files is likely to be a 
site configuration option (perhaps as part of the setup of the batch 
system), so something like the etc/lam* files sounds like a better place 
to configure the location.

Additional options for run-time override include an environment variable 
or options to mpirun.


Brian W. Barrett wrote:
> Hey all -
> A couple changes to LAM's configure script that directly affect you:
>  To configure, add all the normal options you might have (prefix,
> --with-debug, whatever).  For the C/R related stuff, there are only two
> options:
>   --with-cr=DIR
> and
>   --with-cr-file-dir=DIR
> Where --with-cr=DIR will specify DIR as where to look for the src tree of
> the C/R code.  If the headers and libs are in the standard search paths,
> the right things will "just happen" without this flag.
> For the second option, --with-cr-file-dir=DIR, DIR is the default location
> for dropping checkpoint files.  There is currently no $HOME expansion or
> anything like that.  SO this might not be all that useful.  Even more
> important, it probably doesn't work.  So, this will require some more
> thought and/or work.
> Suggestions on where to put the checkpoint files are welcome :).
> Brian

Paul H. Hargrove                          PHHargrove_at_lbl_dot_gov
Future Technologies Group
HPC Research Department                   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory     Fax: +1-510-495-2998