[llvm-bugs] [Bug 35511] New: Build ordering / dependency problems

via llvm-bugs llvm-bugs at lists.llvm.org
Sun Dec 3 23:15:56 PST 2017


            Bug ID: 35511
           Summary: Build ordering / dependency problems
           Product: Build scripts
           Version: trunk
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: cmake
          Assignee: unassignedbugs at nondot.org
          Reporter: codeman.consulting at gmail.com
                CC: llvm-bugs at lists.llvm.org

The last few times I've built trunk LLVM (Usually with just standard llvm and
clang + extra utils) I get some kind of makefile or solution ordering problem
for the all target.  This happens on both Ubuntu 16.04 building with GCC and
with Visual Studio 2015 and 2017.  The symptoms are usually that the build will
complete to around 90% then one of libClang or llvm-lto will fail to link. 
Running make again (or the VS solution, take your pick), will get a few more
files to build.  The current linux build from a fresh cmake generated makefile
build system took 5 tries before every project would complete and make install
works.  The visual studio build took 3 runs the last time I built it.  I think
there's an ordering issue somewhere but I haven't been able to pinpoint it.  I
updated to the most recent CMake on Windows and that broke everything entirely,
creating a "NATIVE" directory under the build directory and putting some things
there, some in x64/Release, and some in Release/x64, so naturally it couldn't
find libraries during link and failed.  I haven't sorted that yet, but I may
just need to revert CMake and stop trying to use LTO.  The linux one is
definitely odd though, as it was building fine a few months ago on the same

Is anyone else seeing this type of ordering issue?  I've done hundreds of
builds of LLVM using CMake and never run into this kind of issue on a supported
OS before.

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/20171204/35027fb6/attachment-0001.html>

More information about the llvm-bugs mailing list