[prev in list] [next in list] [prev in thread] [next in thread]
List: llvm-bugs
Subject: [llvm-bugs] [Bug 31812] New: libLLVMSupport.a gets linked twice during CMake based builds
From: via llvm-bugs <llvm-bugs () lists ! llvm ! org>
Date: 2017-01-31 11:31:10
Message-ID: bug-31812-206 () http ! llvm ! org/bugs/
[Download RAW message or body]
--1485862271.3dFC0.10557
Date: Tue, 31 Jan 2017 05:31:11 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
https://llvm.org/bugs/show_bug.cgi?id=31812
Bug ID: 31812
Summary: libLLVMSupport.a gets linked twice during CMake based
builds
Product: Build scripts
Version: 3.9
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: cmake
Assignee: unassignedbugs@nondot.org
Reporter: Awais_Belal@mentor.com
CC: llvm-bugs@lists.llvm.org
Classification: Unclassified
Cross building LLVM 3.9.1 sometimes fail reporting undefined symbols in
libLLVMSupport static library. Doing a bit of log digging shows that
libLLVMSupport gets linked twice (both for NATIVE and target builds) and when
this multiple linking step takes place concurrently the libLLVMSupport static
library gets corrupted and the mentioned build failure is seen.
This was discussed on the llvm-dev mailing list and I was asked to report this
here. The mailing list entry is:
http://lists.llvm.org/pipermail/llvm-dev/2017-January/109570.html
--
You are receiving this mail because:
You are on the CC list for the bug.
--1485862271.3dFC0.10557
Date: Tue, 31 Jan 2017 05:31:11 -0600
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - libLLVMSupport.a gets linked twice during CMake based builds"
href="https://llvm.org/bugs/show_bug.cgi?id=31812">31812</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>libLLVMSupport.a gets linked twice during CMake based builds
</td>
</tr>
<tr>
<th>Product</th>
<td>Build scripts
</td>
</tr>
<tr>
<th>Version</th>
<td>3.9
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>cmake
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>Awais_Belal@mentor.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>Cross building LLVM 3.9.1 sometimes fail reporting undefined symbols in
libLLVMSupport static library. Doing a bit of log digging shows that
libLLVMSupport gets linked twice (both for NATIVE and target builds) and when
this multiple linking step takes place concurrently the libLLVMSupport static
library gets corrupted and the mentioned build failure is seen.
This was discussed on the llvm-dev mailing list and I was asked to report this
here. The mailing list entry is:
<a href="http://lists.llvm.org/pipermail/llvm-dev/2017-January/109570.html">http://lists.llvm.org/pipermail/llvm-dev/2017-January/109570.html</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>
--1485862271.3dFC0.10557--
[Attachment #3 (text/plain)]
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic