<html>#2772: Issues link against Kadath thorns and Intel MKL due to link ordering
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>tootle</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></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 tootle):</p>
<p>This is still in the dev branch as I need to test it more thoroughly with the build script. I also ran into an issue on frontier where the external libs linked against didn’t match the libs the fuka library was built with when the external libraries found the local libraries on their own. In this case FUKA was built independently of the ETK build. I think if it is built from scratch during the ET build process and I can ensure the importer functions correctly, then this will be sufficient for now. If people want to build ETK with a prebuilt FUKA, then they will need to be more careful - which I’ll add to the documentation once the details are flushed out</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2772/issues-link-against-kadath-thorns-and'>https://bitbucket.org/einsteintoolkit/tickets/issues/2772/issues-link-against-kadath-thorns-and</a></p>
</html>