<html>#2185: PAPI's compilation produces warnings
<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>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2019_10</td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>blocker</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Changes (by Roland Haas):</p>
<p><table>
<tr><td>priority:</td><td>blocker (was minor)</td></tr>
<tr><td>milestone:</td><td>ET_2019_10 (was )</td></tr>
</table></p>
<p>PAPI's build procedure currently contains two failing parts, one that shows up as error messages along the lines of "libthorn_PAPI.a_tests cannot be build" which is caused by Cactus setting a NAME variable in MAKEFLAGS which overrides what PAPI's Makefile wants to use and once that is finished, the tests actually fail to run since eg OpenMP libraries are missing.</p>
<p>The attached patch gets rid of NAME and builds only the parts we need. </p>
<p>The $(pwd)/libpfm4/lib/libpfm.a path is copied from the Makefile (Rules.pfm4_pe I believe).</p>
<p><strong>Keyword:</strong> PAPI</p>
<p>Comment (by Roland Haas):</p>
<p>Prevents built on OSX Macports</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2185/papis-compilation-produces-warnings'>https://bitbucket.org/einsteintoolkit/tickets/issues/2185/papis-compilation-produces-warnings</a></p>
</html>