<html>#2428: Possible issue between ExternalLibraries/FFTW3 thorn and the Cactus/lib/sbin/strip-incdirs.sh script
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Federico Cipolletta</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>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Federico Cipolletta):</p>
<p>I would like to add one NOTE like the following in each of the documentation (e.g. at section B2.2 of Cactus User Guide):</p>
<p></p>
<p>“<strong>NOTE:</strong> each thorn contained in Cactus/arrangements/ExternalLibraries will automatically adopt the library version contained in the <code>Cactus/arrangements/<library>/dist</code> folder. If another location is specified via the <code>THORN_DIR</code> variable in the <code>machine.cfg</code> file at compilation, then the <code>Cactus/lib/sbin/strip-incdirs.sh</code> script will automatically strip away (for safety reasons) the locations:</p>
<p><code>1. /include</code> </p>
<p><code>2. /usr/include</code> </p>
<p><code>3. /usr/local/include</code> </p>
<p>locations. Therefore, if there is any need for using one already installed version of one external library, the aforementioned location should be avoided (e.g. indicating <code>/home</code> as the <code>THORN_DIR</code> will work with no problems if the required library is installed there).”</p>
<p></p>
<p>Do you agree with that? </p>
<p>Can I simply edit the checkout file from github, commit it and push (as I have been added to the ET developers)?</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2428/possible-issue-between-externallibraries'>https://bitbucket.org/einsteintoolkit/tickets/issues/2428/possible-issue-between-externallibraries</a></p>
</html>