[LLVMbugs] [Bug 14417] New: Due to base compiler upgrade, clang fails to generate binaries on DragonFly 3.2+

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Thu Nov 22 14:30:07 PST 2012


             Bug #: 14417
           Summary: Due to base compiler upgrade, clang fails to generate
                    binaries on DragonFly 3.2+
           Product: clang
           Version: 3.1
          Platform: PC
        OS/Version: DragonFly BSD
            Status: NEW
          Severity: normal
          Priority: P
         Component: Driver
        AssignedTo: unassignedclangbugs at nondot.org
        ReportedBy: draco at marino.st
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

Created attachment 9585
  --> http://llvm.org/bugs/attachment.cgi?id=9585
Fix search path for clang on latest DragonFly releases

DragonFly is unique in that it has two base compilers.  For a few years, those
compilers were gcc 4.1 and gcc 4.4.  At first gcc 4.1 was the primary compiler,
and now gcc 4.4 is the primary compiler.

For the latest release, gcc 4.7 was brought into base and gcc 4.1 removed.  At
this point, clang stopped working on DragonFly because it had gcc41 in its
internal search path.

The clang driver looks for crt* stuff in /usr/lib/gcc41, which no longer
exists.  The standard c++ library is also located there.

The attached patch changes the driver to first look in /usr/lib/gcc47 and then
fallback to /usr/lib/gcc44.  The fallback should guarantee that the latest
clangs run on several past releases of DragonFly BSD as well as the latest

The patches were generated against clang release 3.1.

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.

More information about the llvm-bugs mailing list