<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 --- - GCC Toolchain discovery on Solaris"
href="https://llvm.org/bugs/show_bug.cgi?id=24606">24606</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GCC Toolchain discovery on Solaris
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>3.6
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Sun
</td>
</tr>
<tr>
<th>OS</th>
<td>Solaris
</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>Driver
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedclangbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>stefan.teleman@oracle.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>This is a placeholder bug for a patch submission I will do very shortly.
Summary:
The discovery of the GCC Toolchain location in Solaris is currently not
optimal. It relies on hardcoded paths, and these hardcoded paths are,
by now, obsolete. The result is that, for many recent Solaris versions,
this does not really work.
I will provide a patch which enables the dynamic discovery of a GCC
installation in Solaris 11 or higher, based on our GCC Solaris installation
conventions.
We have a number of clang and llvm patches for Solaris, and we have every
intention of contributing them to the project. This is just the first of
several bugs with follow-up patches that I will be filing.</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>