<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 --- - Cannot specify Exec format for non-native flavors"
href="https://llvm.org/bugs/show_bug.cgi?id=25229">25229</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Cannot specify Exec format for non-native flavors
</td>
</tr>
<tr>
<th>Product</th>
<td>lld
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</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>All Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>alexchandel@gmail.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>Attempting to run `lld -flavor gnu` with a COFF executable produces an error
similar to "Cannot open coff.o: Exec format error".
While some options only apply to one format, for example "-macosx_version_min",
there's no general reason why each flavor should be locked to a specific
executable format, given that LLVM is capable of understanding multiple. For
example, `lld -flavor gnu -target i686-pc-windows-gnu coff.o` should be enough
to cause LLD to emit a PE/COFF executable while accepting GNU-flavored options,
like "-L<dir>" or "-l<libName>". This even has the advantage of providing a
unified linker interface.
Is there any reason this should not be implemented?</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>