[petsc-dev] worthless information

[Matthew Knepley]

On Tue, Aug 30, 2011 at 6:22 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
> On Aug 30, 2011, at 1:19 PM, Satish Balay wrote:
>
> > On Tue, 30 Aug 2011, Barry Smith wrote:
> >
> >>
> >> Compilers:
> >>  C Compiler:         /home/balay/petsc-dev/arch-cuda-double/bin/mpicc
> >>
> >>
> >>   It should also print the underlying compiler that is used by mpicc.
> >
> > Right now - configure.log is the location for details. [and wrt
> > --download stuff - make.log also has the configure command which has
> > the details]
> >
> > Sure - we don't have everything in summary printed by configure
>
>    Well if room is so tight in the "summary printed by configure" then why
> do we waste room printing
>
> >> C Compiler:         /home/balay/petsc-dev/arch-cuda-double/bin/mpicc
>
>    since that conveys no information. Why not take it out and then there
> will be room for actually providing useful information.
>

I thought this was useful, in that this allows a user to reconstruct what we
are doing. He can find that compiler
and try it when he gets an error. If you intend that we, the developers use
the info, I am fine with the log.

   Matt


>   Barry
>
> >
> > Satish
> >
>
>


-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110830/c60b33d9/attachment.html>