[petsc-dev] problem with sub autoconf builds using badly set environmental variables

[Barry Smith]

    If some imbecile has, say FC, set to something and then runs  
PETSc's ./configure using --with-fc=somethingelse then autoconf ./ 
configures started by PETSc (for example --download-mpich)  will use  
the environmental variable instead and thus have incompatible  
compilers and a mess impossible to debug.

    Satish, can we have PETSc's config/configure.py STOP if any of the  
those dangerous variables are set and tell the user to get rid of them  
before running ./configure to prevent this problem and our wasted time  
on petsc-maint's?

    Thanks

     Barry



Begin forwarded message:

> From: "Zhao Y." <yz1c08 at soton.ac.uk>
> Date: January 11, 2010 2:32:21 PM CST
> To: petsc-maint Maintenance <petsc-maint at mcs.anl.gov>
> Subject: [petsc-maint #40116] Problem with installation
> Reply-To: petsc-maint at mcs.anl.gov, "Zhao Y." <yz1c08 at soton.ac.uk>
>
> Hi, the log file is attached.Please help me figure the problem out.
>
> Yours sincerely
> Yu Zhao
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configure.log
Type: application/octet-stream
Size: 253280 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100111/35710df8/attachment.obj>
-------------- next part --------------