[llvm-bugs] [Bug 34793] New: Mac OS tarballs do not provide usable linker

via llvm-bugs llvm-bugs at lists.llvm.org
Sat Sep 30 23:55:10 PDT 2017


            Bug ID: 34793
           Summary: Mac OS tarballs do not provide usable linker
           Product: Packaging
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: binary tarballs
          Assignee: unassignedbugs at nondot.org
          Reporter: richard-llvm at metafoo.co.uk
                CC: llvm-bugs at lists.llvm.org

Installing the Mac OS "clang" tarball on a Mac OS system almost provides a
usable toolchain, but fails to do so because the compiler can't run the linker.

The Mac OS tarball contains two symlinks to the lld binary: lld-link (a Windows
link.exe-compatible linker driver), and ld.lld (a GNU ld-compatible linker
driver). It does not provide an "ld" symlink, so the shipped version of clang
does not use the shipped version of lld. (And -fuse-ld=lld doesn't work either,
see PR34792).

Creating a symlink from lld to ld in the bin directory is /almost/ enough for
our release tarball to contain a working toolchain -- one must also remove the
"-lto_library blah" flag that clang adds to the linker command line to work
around PR32175. (LLD emits a couple of warnings about flags that Clang passes
it that it doesn't fully understand, but they seem harmless.)

Presumably we do intend for the Clang and LLD binaries we ship in the Mac OS
release tarball to be usable together to produce Mac OS binaries?

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/20171001/fddf114a/attachment-0001.html>

More information about the llvm-bugs mailing list