[llvm-bugs] [Bug 25118] New: Usage of #include_next breaks compilation

via llvm-bugs llvm-bugs at lists.llvm.org
Thu Oct 8 16:03:20 PDT 2015


https://llvm.org/bugs/show_bug.cgi?id=25118

            Bug ID: 25118
           Summary: Usage of #include_next breaks compilation
           Product: libc++
           Version: 3.7
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: ldionne.2 at gmail.com
                CC: llvm-bugs at lists.llvm.org, mclow.lists at gmail.com
    Classification: Unclassified

On trunk, libc++ currently uses #include_next, which can break compilation
with -Werror because #include_next is flagged as a language extension.
See [1] for an example.

The breaking changes seems to be introduced by the commits in the range
[r249738, 249761] by Richard Smith.

Regards,
Louis

[1]: https://travis-ci.org/ldionne/hana/jobs/84381855#L1410

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20151008/1b4d4df8/attachment-0001.html>


More information about the llvm-bugs mailing list