<html>#2572: Build failure in PITTNullCode SphericalHarmonicReconGen
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Wolfgang Kastaun</td></tr>
<tr><td style='text-align:right'> Status:</td><td>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>ET_2021_05</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>Interesting. Ok. The Silo one is an actual bug in HDF5 since it’s symbols are not internally consistent. This one here may be different though even so the newsletter “[…]that includes deprecated symbols (the default)[…]” to me would read as if the default settings should be a backwards compatible API (which of course Arch Linux may change if they want to be on the bleading edge).</p>
<p>I will give this a try on my workstation with a self-compiled HDF5 1.12.</p>
<p>Semantic versioning by HDF5 would be great so that API change → major version change. But then, with the Linux kernel now also updating major version numbers when the devs run out of fingers and toes to count, this is probably a futile hope…</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2572/build-failure-in-pittnullcode'>https://bitbucket.org/einsteintoolkit/tickets/issues/2572/build-failure-in-pittnullcode</a></p>
</html>