<html>#2553: Cactus' link command uses CPPFLAGS and CXXFLAGS
<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></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>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>The ticket got sidetracked a bit. The original question was to remove <code>CPPFLAGS</code> and <code>CXXFLAGS</code> from the link call since there is no actual compilation happening (it really only links library and object files).<br>
Removing <code>CXXFLAGS</code> may result in (fixable) build failures in option lists that set eg <code>-fopenmp</code> only in <code>CXXFLAGS</code> and not also in <code>LDFLAGS</code> (or <code>OPENMP_CXXFLAGS</code> and not also <code>OPENMP_LDFLAGS</code>) since <code>-fopenmp</code> must be present in the link line to link in the OpenMP runtime libraries.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2553/cactus-link-command-uses-cppflags-and'>https://bitbucket.org/einsteintoolkit/tickets/issues/2553/cactus-link-command-uses-cppflags-and</a></p>
</html>