<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 14, 2010, at 8:54 PM, Matthew Knepley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Do we really want the full path to all compilers? We discussed this before and did not<div>do it. Satish, do you remember why?</div></blockquote><div><br></div> With the full path I like the fact that the compiler choices are set at at ./configure time and won't mysteriously change (and result in failure) later if someone changes their path or installs a new MPI into the path.</div><div><br></div><div> I do not know why you opted not to always have the full path.<br><blockquote type="cite"><div><br></div><div> Matt<br><br><div class="gmail_quote">On Tue, Sep 14, 2010 at 8:51 PM, Lisandro Dalcin <span dir="ltr"><<a href="mailto:dalcinl@gmail.com">dalcinl@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 14 September 2010 22:26, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
><br>
> On Sep 14, 2010, at 8:24 PM, Lisandro Dalcin wrote:<br>
><br>
>> On 14 September 2010 21:55, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
>>><br>
>>> On Sep 14, 2010, at 6:24 PM, Lisandro Dalcin wrote:<br>
>>><br>
>>>> 1) If mpicc is in $PATH, then petscvariables will get PCC=mpicc.<br>
>>>> Perhaps it should get the full path instead?<br>
>>>><br>
>>>> 2) I think CXX and FC variables should be renames to PCXX and PFC. The<br>
>>>> former names can easily conflict with CXX and FC defined in user<br>
>>>> makefiles for use with non-MPI sources.<br>
>>><br>
>>> Then we should also get rid of CC<br>
>>><br>
>>> Essentially you are saying we should remove all "traditional" use of these variables from our makefiles? I agree doing that might be a good idea. But doesn't it contradict your attempt to try hard to conform to standard usage for things?<br>
>>><br>
>><br>
>> Sorry, I need a clarification: Could you tell me why PETSc makefiles<br>
>> uses PCC instead of the "traditional" CC? Is it just because PCC<br>
>> could be CC or CXX depending on --with-c-language?<br>
><br>
> Yes that is one reason and may be the only reason.<br>
><br>
<br>
</div>In such case, forget my comments, except for the part of setting<br>
PCC=/path/to/mpicc (and perhaps the same for CC, CXX, FC if they point<br>
to MPI compiler wrappers). What do you think about this? Please note<br>
I'm not objecting the current status, just asking about the full path<br>
alternative.<br>
<div><div></div><div class="h5"><br>
<br>
--<br>
Lisandro Dalcin<br>
---------------<br>
CIMEC (INTEC/CONICET-UNL)<br>
Predio CONICET-Santa Fe<br>
Colectora RN 168 Km 472, Paraje El Pozo<br>
Tel: +54-342-4511594 (ext 1011)<br>
Tel/Fax: +54-342-4511169<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener<br>
</div>
</blockquote></div><br></body></html>