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

Matthew Knepley knepley at gmail.com
Tue Mar 19 00:52:27 CDT 2013


On Mon, Mar 18, 2013 at 9:27 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

>
> On Mon, Mar 18, 2013 at 8:24 PM, Matthew Knepley <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?
>

We had not tried that. It might work.

   Matt

-- 
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/20130319/3569cc05/attachment.html>


More information about the petsc-dev mailing list