[LLVMbugs] [Bug 13187] New: The version of GCC that clang/llvm partners with is baked-in.

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=13187

             Bug #: 13187
           Summary: The version of GCC that clang/llvm partners with is
                    baked-in.
           Product: clang
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: -New Bugs
        AssignedTo: unassignedclangbugs at nondot.org
        ReportedBy: dwalker07 at yahoo.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified


Looking at
<http://stackoverflow.com/questions/10308167/when-enabling-c11-with-stdlibc-4-7-clang-error-out-while-gcc-compiles-fine>,
which I added a comment to one answer, it seems that CLang (and/or LLVM)
automatically chooses which GCC to base its headers and libraries from.  This
is a problem if the user has multiple editions of GCC installed and the
automatically-chosen one, most likely the system compiler, is not the one the
user wanted.  (A good example is needing a bleeding-edge version for C++11
support, which no system compiler has.)  There are command-line options to
screw around with the include directories, but it's neither a simple nor
complete workaround.

What I'm looking for is a command-line option that is a total override to the
partner GCC, ignoring any baked-in paths.  (It's not acceptable that the only
complete override of which GCC to use is at compile-time (of CLang/LLVM).)

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.