pisses me off to no end

Matthew Knepley knepley at gmail.com
Wed Jun 10 17:19:39 CDT 2009

On Wed, Jun 10, 2009 at 4:43 PM, Barry Smith <BSMITH at mcs.anl.gov> wrote:

> Using C/C++ compiler: /Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpicc
> -Wall -Wwrite-strings -Wno-strict-aliasing -g3
> C/C++ Compiler version:
> Using Fortran compiler: /Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpif90
> -Wall -Wno-unused-variable -g
> Fortran Compiler version:
> -----------------------------------------
> Using C/C++ linker: /Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpicc
> Using Fortran linker: /Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpif90
>  This is the most useless piece of shit information I have seen in my
> entire life! It tells me NOTHING about what compiler is being used.
> I want the mpicc -show and mpif90 -show to be printed in make.log if an MPI
> compiler is being used! How can we figure out what is going
> on when we don't even know what compiler is being used?

I am not opposed to this, but it ONLY works for mpich. Is there any
generality for mpicc?

>  Plus NO information about the linker options that are used are put into
> make.log!! That information needs to go in there also.

I agree. Fixed.


>  Debugging failed builds for other people is painful enough but when we
> shoot ourselves in the foot by not putting the information we need in the
> log files we make it ten times worse.
>  Please fix this.
>   Barry
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20090610/af0df38e/attachment-0001.html>

More information about the petsc-dev mailing list