[petsc-dev] Why does configure ignore compiler output?

[Richard Tran Mills]

I seem to recall that compilers on Cray systems were (and still are) 
huge offenders in the spewing meaningless output department.  I like the 
"blacklist" suggestion.

--Richard

On 3/18/13 9:27 PM, Jed Brown wrote:
>
> On Mon, Mar 18, 2013 at 8:24 PM, Matthew Knepley <knepley at gmail.com 
> <mailto:knepley at gmail.com>> wrote:
>
>     You can always turn that switch off for your test. What we were
>     finding is that some crappy compilers
>     were killing everything by putting in meaningless output for every
>     compile. We don't rip it out because
>     maybe those compilers die and we flip the switch in the new release.
>
>
> What about a blacklist containing output that we do interpret as failure?


-- 
Richard Tran Mills, Ph.D.
Computational Earth Scientist      | Joint Assistant Professor
Hydrogeochemical Dynamics Team     | EECS and Earth & Planetary Sciences
Oak Ridge National Laboratory      | University of Tennessee, Knoxville
E-mail: rmills at ornl.gov  V: 865-241-3198 http://climate.ornl.gov/~rmills

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130319/614734a6/attachment.html>