[llvm-bugs] [Bug 25597] New: Fix c++ support on recent DragonFly BSD releases

via llvm-bugs llvm-bugs at lists.llvm.org
Sat Nov 21 14:33:15 PST 2015


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

            Bug ID: 25597
           Summary: Fix c++ support on recent DragonFly BSD releases
           Product: clang
           Version: trunk
          Hardware: PC
                OS: DragonFly BSD
            Status: NEW
          Severity: normal
          Priority: P
         Component: Driver
          Assignee: unassignedclangbugs at nondot.org
          Reporter: draco at marino.st
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

Created attachment 15328
  --> https://llvm.org/bugs/attachment.cgi?id=15328&action=edit
Update clang driver to support current DragonFly BSD out of the box

Clang support for DragonFly BSD is lagging a bit, resulting in poor support for
c++.

DragonFlyBSD is unique in that it has two base compilers.  At the time of the
last Clang update for DragonFly, these compilers were GCC 4.4 and GCC 4.7
(default).

With DragonFly Release 4.2, GCC 4.4 was replaced with GCC 5.0, partially
because the C++11 support of GCC 4.7 was incomplete.  The DragonFly project
will Release version 4.4 soon.

This patch updates the Clang driver to use libstdc++ from GCC 5.2  The support
for falling back to the alternate compiler was removed for two reasons:

1) The last release to use GCC 4.7 is DF 4.0 which has already reached EOL
2) GCC 4.7 libstdc++ is insufficient for many "ports"

Therefore, I think it is reasonable that the development version of clang
expects GCC 5.2 to be in place and not try to fall back to another compiler.

The attached patch will do this.  The Tools.cpp file was signficantly modified
to fix the linking which had been changed somewhere along the line.  The rest
of the changes should be self-explanatory.

-- 
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/20151121/ebaf7e2a/attachment.html>


More information about the llvm-bugs mailing list