[llvm-bugs] [Bug 24390] New: Diagnostic "#include_next in primary source file" when processing header files

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Aug 7 06:15:54 PDT 2015


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

            Bug ID: 24390
           Summary: Diagnostic "#include_next in primary source file" when
                    processing header files
           Product: clang
           Version: 3.7
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: libclang
          Assignee: unassignedclangbugs at nondot.org
          Reporter: nikolai.kosjar at theqtcompany.com
                CC: klimek at google.com, llvm-bugs at lists.llvm.org
    Classification: Unclassified

---8<--- shell session start ---8<---
% cat -n header.hpp                                        
     1    #include_next <iostream>
% /usr/bin/clang-3.6 -fsyntax-only -x c++-header header.hpp
header.hpp:1:2: warning: #include_next in primary source file
#include_next <iostream>
 ^
1 warning generated.
% 
---8<--- shell session end ---8<---

This warning is expected when using clang as a compiler. However, it also
occurs when using libclang. There does not seem to be an option to disable this
warning.

-- 
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/20150807/d0f61b77/attachment.html>


More information about the llvm-bugs mailing list