<html>#2439: MakeThornList issues
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Steven R. Brandt</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></td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>I cannot really make the script default to <code>repos/manifest/einsteintoolkit.th</code> since the script is in Cactus and not the ET. There are already defaults for the master thornlist (that I am inheriting from Ian’s implementation):</p>
<blockquote>
<p>If this option is not<br />
used, and the environment variable $CACTUSRC has been set, the<br />
file $CACTUSRC/.cactus/MasterThornList will be used, otherwise the<br />
file $HOME/.cactus/MasterThornList will be used.</p>
</blockquote>
<p>and in fact also “ThornList” in that location (again inherited from Ian’s code).</p>
<p>To clarify: when passing multiple parfiles you would like to create a thornlist that can run any of those parfiles? Note that this can cause conflicts since some thorns cannot be compiled into the same executable (due to conflicting symbols), so making this work with a guarantee of no error messages when building is not quite a simple as just concatenating the parfiles when reading them. To trigger this one also needs to supply a master thorn list with both conflicting thorns listed (which ours is not because it can be compiled).</p>
<p>Relaxing this restriction then yes, supporting multiple parfiles is easy. I’ll post a pull request.</p>
<p></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2439/makethornlist-issues'>https://bitbucket.org/einsteintoolkit/tickets/issues/2439/makethornlist-issues</a></p>
</html>