silence some try.c warnings
authorH.Merijn Brand - Tux <h.m.brand@xs4all.nl>
Thu, 21 Apr 2016 11:18:45 +0000 (13:18 +0200)
committerH.Merijn Brand - Tux <h.m.brand@xs4all.nl>
Thu, 21 Apr 2016 11:18:45 +0000 (13:18 +0200)
commit7de2f3a3c68fb51be35cdc5c3cd0e3d5df9052b8
treeb060cd7cfa311ceeacec03c7f2662e69a8a74f5b
parent733156e21a93029d6213e242872791dddee6c241
silence some try.c warnings

Backport from cc0bf92f2c5d6a67a850efa7d21a5a83e016d446
Author: David Mitchell <davem@iabyn.com>
Date:   Mon Mar 14 16:49:05 2016 +0000

    Configure: silence some try.c warnings

    On one of the try.c compilations, redirect stderr to /dev/null, since
    the code can legitimately warn without there being a problem.

    The try.c in question is probing for what symbols the compiler supports.
    The clang extensions __has_include and __has_include_next are designed
    only to be used in .h files, so they warn if used from try.c
U/modified/Cppsym.U