<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div> Aron,<div><br></div><div> Your complaints about PETSc's ./configure are legitimate, there is no documentation and the --help spews a bunch of incoherent, badly formatted and inconsistent information. In addition there is no documentation about parts of autoconf it supports versus what parts of autoconf it does not support.</div><div><br></div><div> I have gone through all the help strings to use more consistent notation and improve the formatting; I think --help is much better now in petsc-dev. </div><div><br></div><div> It would be possible to generate a .html version of the help automatically, but for it to be useful we should add more information into the .py that describe the options more fully. Let's think about this.</div><div><br></div><div><br></div><div> Barry</div><div><br></div><div><br><div><div>On Jul 26, 2010, at 1:00 PM, Aron Ahmadia wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Barry and Satish,<br><br>While I have your eyes, we should probably discuss what the ideal way for me<br>to tell PETSc how my system is set up.<br><br>As you can probably tell, I am doing a lot of the user environment<br>configuration for our BlueGene using modules and some Python scripting to<br>back them up, so softenv+some more magic on the administrator side to<br>streamline the process. This isn't my full time job, but I'd like to do it<br>right.<br><br>I like the idea of telling PETSc how to use each of the packages, but right<br>now the usage is not well-defined. There's a huge dump of available options<br>if you type configure -h but no good documentation on the .py files that I<br>know of. In fact, it might be useful to be able to generate an HTML page<br>that lists all the options and what they do.<br><br>I think I have gotten things working, both by careful .py file definitions<br>and also by jamming all of my link flags and libraries into LIBS. Perhaps<br>we should break them in to LDFLAGS and LIBS? I am okay with explicitly<br>giving PETSc my intended environment variables, this is safer for everyone.<br><br><br>If there's a way I can help on this, let me know. I need to remember to<br>only bang my head against PETSc problems when you guys are awake :)<br><br>A<br><br>On Mon, Jul 26, 2010 at 8:45 PM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite"> Satish,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> It is missing Aron's favorite. Could you please add it LDFLAGS<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> I was expecting it up in config/configure.py before anything else? Won't<br></blockquote><blockquote type="cite">that be a better place for it?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Barry<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Jul 26, 2010, at 12:13 PM, Satish Balay wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">On Mon, 26 Jul 2010, Barry Smith wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On Jul 26, 2010, at 12:04 PM, Satish Balay wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Barry,<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I've added code in petsc-dev that warns users of the env variables<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">[does not ask them to unset]. It then ignores these values - and never<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">uses them in configure process.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> Where is the check, I cannot find it anywhere?<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">resetEnvCompilers() in setCompilers.py.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Perhaps we need to add more variables in that list..<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Satish<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><br><div dir="ltr">Barry and Satish,<div><br></div><div>While I have your eyes, we should probably discuss what the ideal way for me to tell PETSc how my system is set up.</div><div><br></div><div>As you can probably tell, I am doing a lot of the user environment configuration for our BlueGene using modules and some Python scripting to back them up, so softenv+some more magic on the administrator side to streamline the process. This isn't my full time job, but I'd like to do it right.</div>
<div><br></div><div>I like the idea of telling PETSc how to use each of the packages, but right now the usage is not well-defined. There's a huge dump of available options if you type configure -h but no good documentation on the .py files that I know of. In fact, it might be useful to be able to generate an HTML page that lists all the options and what they do.</div>
<div><br></div><div>I think I have gotten things working, both by careful .py file definitions and also by jamming all of my link flags and libraries into LIBS. Perhaps we should break them in to LDFLAGS and LIBS? I am okay with explicitly giving PETSc my intended environment variables, this is safer for everyone. </div>
<div><br></div><div>If there's a way I can help on this, let me know. I need to remember to only bang my head against PETSc problems when you guys are awake :)</div><div><br>A</div><div><br><div class="gmail_quote">On Mon, Jul 26, 2010 at 8:45 PM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Satish,<br>
<br>
It is missing Aron's favorite. Could you please add it LDFLAGS<br>
<br>
I was expecting it up in config/configure.py before anything else? Won't that be a better place for it?<br>
<font color="#888888"><br>
<br>
Barry<br>
</font><div><div></div><div class="h5"><br>
On Jul 26, 2010, at 12:13 PM, Satish Balay wrote:<br>
<br>
> On Mon, 26 Jul 2010, Barry Smith wrote:<br>
><br>
>><br>
>> On Jul 26, 2010, at 12:04 PM, Satish Balay wrote:<br>
>><br>
>>> Barry,<br>
>>><br>
>>> I've added code in petsc-dev that warns users of the env variables<br>
>>> [does not ask them to unset]. It then ignores these values - and never<br>
>>> uses them in configure process.<br>
>><br>
>> Where is the check, I cannot find it anywhere?<br>
><br>
> resetEnvCompilers() in setCompilers.py.<br>
><br>
> Perhaps we need to add more variables in that list..<br>
><br>
> Satish<br>
><br>
<br>
</div></div></blockquote></div><br></div></div>
</blockquote></div><br></div></body></html>