<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:kai@dev.carbon-project.org" title="Kai <kai@dev.carbon-project.org>"> <span class="fn">Kai</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - g++: error: unrecognized command line option ‘-std=c++14’"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111458">bug 111458</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>kai@dev.carbon-project.org
</td>
<td>
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - g++: error: unrecognized command line option ‘-std=c++14’"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111458#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - g++: error: unrecognized command line option ‘-std=c++14’"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111458">bug 111458</a>
from <span class="vcard"><a class="email" href="mailto:kai@dev.carbon-project.org" title="Kai <kai@dev.carbon-project.org>"> <span class="fn">Kai</span></a>
</span></b>
<pre>This is known and was discussed in the MR for this change, see the thread
starting at
<a href="https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1706#note_210239">https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1706#note_210239</a>
GCC 4.8 is no longer supported upstream (last release was in 2015), just as GCC
5 and GCC 6 are no longer supported upstream. Therefore I would be inclined to
close this bug as "wontfix", though I guess this is not up to me. I'll leave
this decision up to somebody like Dave, who merged my MR, and has more
seniority within Mesa.
Personally I will not prepare any patch to fix this since GCC 4.8 is no longer
supported upstream and you would have to run at least an Distribution like
Debian oldoldstable (Jessie), which is on its last stretch of LTS. IMHO the
burden to keep such ancient software working has to fall on people choosing to
run unsupported versions of eg. GCC. Because reverting this change would mean
that the users of a current toolchain would be required to carry local patches
instead, which doesn't seem like a sensible solution to me.
I hope this doesn't come across too strongly. You have commit rights AFAIR,
therefore you could always supersede me and revert my patch. Though I'd really
like to know how building with a current toolchain is meant to happen then.
AFAIK Mesa is meant to be built against LLVM 10 as there are special cases for
LLVM 10 in the code for RadeonSI and Clover.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>