[petsc-dev] BuildSystem: PCC=mpicc, CXX and FC
Barry Smith
bsmith at mcs.anl.gov
Wed Sep 15 10:54:53 CDT 2010
On Sep 15, 2010, at 8:10 AM, Satish Balay wrote:
> On Wed, 15 Sep 2010, Barry Smith wrote:
>
>>
>> On Sep 14, 2010, at 11:03 PM, Satish Balay wrote:
>>
>>> I don't remember previous conversation regarding it. However wrt
>>> python I strongly felt the python used by configure should be used by
>>> 'full path' in generated scripts. [for eg check: reconfigure.py]
>>>
>>> I'm fine with using full paths for default searches done by configure
>>> [cc,mpicc etc from PATH]. However if user provides 'cc=gcc' - this
>>> should not be expanded to full PATH automatically by configure..
>>
>> How come?
>
> Primarily because user should be free to choose what he/she wants
>
> CC=gcc vs CC=/usr/bin/gcc
>
> Perhaps this doesn't matter.
I sort of understand but even if we use the full path we are using what they wanted. But it is always what they wanted at configure time.
I vote for trying to hard path everything and see how it goes.
Barry
>
> Satish
More information about the petsc-dev
mailing list