<html>#2660: create autoconf test that checks for too old g++ STL in combination with icpc
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</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>task</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>Compilation of the ET on clusters regularly fails if icpc is combined with a too old STL from g++. As of <a data-is-external-link="true" href="https://www.einsteintoolkit.org/about/releases/ET_2022_05_announcement.html" rel="nofollow">https://www.einsteintoolkit.org/about/releases/ET_2022_05_announcement.html</a> the ET must be compiled with STL from gcc-6 (or later) when using icpc to provide for full C++11 support (and not technical preview C++11).</p>
<p>Similarly before, using gcc-4.3 (default on some redhat systems) will fail to compile vectors due to bad default constructors.</p>
<p>We should construct an autoconf test that tests for these issues and reports a useful error message to users setting up Cactus / the ET on their cluster. Note that technically Cactus would work with older C++ compilers but the Einstein Toolkit will not.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2660/create-autoconf-test-that-checks-for-too'>https://bitbucket.org/einsteintoolkit/tickets/issues/2660/create-autoconf-test-that-checks-for-too</a></p>
</html>