<html>#2679: How to link an externally compiled library during ET compilation
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Maria Mutz</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>bug</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>Comment (by Roland Haas):</p>
<p>This is rather strange. The optioin list looks ok to me to be honest. Adding <code>-lcocalmrns</code> to <code>LDFLAGS</code> is ok.</p>
<p>The error message about missing <code>main</code> is strange since <code>main</code> is provided by the Cactus flesh. Is it possible that the COCAL library defines its own <code>main</code> and that that one interferes? It would be good to see all the error messages and not just the last couple. Would you mind taking a look at <a data-is-external-link="true" href="http://einsteintoolkit.org/support.html#general-guidelines-for-questions" rel="nofollow">http://einsteintoolkit.org/support.html#general-guidelines-for-questions</a> and provide the files described in there, please?</p>
<p>Since COCAL is not part of the Einstein Toolkit (and, at least until the recent past, had an unusual build system), have you contacted the COCAL author (Antonios Toskaros), who may be able to provide advise as well?</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2679/how-to-link-an-externally-compiled-library'>https://bitbucket.org/einsteintoolkit/tickets/issues/2679/how-to-link-an-externally-compiled-library</a></p>
</html>