<html>#2753: Add CarpetX thorns to Einstein Toolkit manifest
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Erik Schnetter</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>proposal</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Other</td></tr>
</table>
<p>Comment (by Samuel Cupp):</p>
<p>Sorry for not responding to this promptly. I do not have a complete list of machines that people are currently using. However, I know for sure people are using Deep Bayou, the INL machines, and Falcon. It looks like Falcon has gcc 12, which I believe has all of the '17 standard. Can you confirm what version of gcc is the minimum for CarpetX currently?</p>
<p>I don’t know what machines the RIT group is using, but it sounded like several of their machines probably don’t have access to C++17 (or anything beyond like 2011…).</p>
<p>I agree with Roland that it would likely be untenable to require C++17 by default to compile the toolkit.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2753/add-carpetx-thorns-to-einstein-toolkit'>https://bitbucket.org/einsteintoolkit/tickets/issues/2753/add-carpetx-thorns-to-einstein-toolkit</a></p>
</html>