<div dir="ltr">Hi Ian, <div><br></div><div>The cfg file I use _is_ the same as the stock osx_macports.cfg. Now however I have, after Steve's suggestion, replaced "MPI_DIR=/opt/local" with "MPI_DIR=" (ie nothing) and tried to build with that. If this assignment needs to be something else, I need for the developers to confirm that. So, I have already tried the stock optionlist with a crash as the result. I sent to query about replacing <a href="http://detect.pl">detect.pl</a> with the version which puts mpiCC last, as that was what I used when I was using the dev version. I am using Hilbert now, since using the dev version resulted in a problem due to it being the case that one day a few weeks ago a change in the dev version resulted in the build crashing. Sticking with Hilbert is what I will do. So my question was can I go ahead and replace the Hilbert <a href="http://detect.pl">detect.pl</a> with the dev version of <a href="http://detect.pl">detect.pl</a>. While I think this is likely ok, I want to proceed carefully. </div><div><br></div><div>I am also looking at the compatibility issue among the various components mpicc, mpixx, openmpi, and hdf5. I am using the patched flavor of hdf5. A while back you thought that the patched version of hdf5 was ok to use, so that is what I am doing (ie the hdf5 is HDF5_DIR = /opt/local). </div><div><br></div><div>The problem I was having was that some updates to macports resulted in inadvertently inducing inconsistencies/incompatibilities dooming the builds. Very frustrating. I have not done a macports update in at least two weeks and have checked the versions of the compiled mpicc, mpixx, openmpi and hdf5 and so far see no problems....I obviously must be missing something if compatibility is the problem. And I will not do a macports update until I can be sure of its effects on the ET builds on my mac running Yosemite.</div><div><br></div><div>Please have patience. Believe me, I want to get to the use of Eloisa's CT_Multilevel thorn as soon as possible!</div><div><br></div><div>Comer </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 7, 2015 at 1:39 PM, Ian Hinder <span dir="ltr"><<a href="mailto:ian.hinder@aei.mpg.de" target="_blank">ian.hinder@aei.mpg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><span class=""><div>On 7 Jul 2015, at 18:55, Comer Duncan <<a href="mailto:comer.duncan@gmail.com" target="_blank">comer.duncan@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">HI Steve,<div><br></div><div>I have reset MPI_DIR= ,i.e. not even a blank and rebuilt, but still get the same crash complaints. Am I to set MPI_DIR to something else? </div><div><br></div><div>I note that in May I had issues with builds in part due to the mpicc vs mpiCC problem on macs. Then in the dev version <a href="http://detect.pl/" target="_blank">detect.pl</a> was changed to put mpiCC last so the mac would not be as confused. I am using the latest release of ET and have looked at the <a href="http://detect.pl/" target="_blank">detect.pl</a> file with that. It does not have the reordering of the search list for mpicc with mpiCC put last, as did the dev version. Somehow I have been assuming that the change to <a href="http://detect.pl/" target="_blank">detect.pl</a> had been backported to Hilbert, but apparently not?? So, is it reasonable to replace the released Hilbert version of <a href="http://detect.pl/" target="_blank">detect.pl</a> with the dev-fixed version? If that can be done safely I could give that a try.</div><div><br></div><div>Thanks for all who help.</div></div></blockquote><div><br></div></span><div>Hi Comer,</div><div><br></div><div>Maybe I missed it, but have you tried using the osx-macports.cfg optionlist that we provide? We tested this, and it worked at the time, with the list of macports packages. I now see you are using a different optionlist. Does the one in simfactory no longer work? Is the issue that you are using the release, and a needed fix has not been backported? </div><div><div class="h5"><br><blockquote type="cite"><div dir="ltr"><div><br></div><div>Comer</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 7, 2015 at 9:08 AM, Steven R. Brandt <span dir="ltr"><<a href="mailto:sbrandt@cct.lsu.edu" target="_blank">sbrandt@cct.lsu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Comer, thank you for sending the
optionlist. I see that you have<br>
<br>
MPI_DIR = /opt/local<br>
<br>
The expectation is that the system can find the mpi c++ compiler
wrapper<br>
in $(MPI_DIR)/bin. Is that the case? The mpi c++ compiler wrapper
may have<br>
any of the following names: mpic++, mpiCC, mpicxx, or
mpicxx-openmpi-mp.<br>
<br>
If the mpi c++ wrapper is in your path, then you could simply try
unsetting<br>
the MPI_DIR variable and building.<br>
<br>
Cheers,<br>
Steve<div><div><br>
<br>
On 07/06/2015 05:33 PM, Frank Loeffler wrote:<br>
</div></div></div>
<blockquote type="cite"><div><div>
<pre>On Mon, Jul 06, 2015 at 03:30:13PM -0400, Comer Duncan wrote:
</pre>
<blockquote type="cite">
<pre>I have tried building ET for the current released version. I am on a
macbook pro running Yosemite. The build script is:
</pre>
</blockquote>
<pre>On first glance, this looks like a problem with a missing c++ mpi
interface (again?). It would be interesting to see your option list and
a verbose link line.
Frank
</pre>
<br>
<fieldset></fieldset>
<br>
</div></div><span><pre>_______________________________________________
Users mailing list
<a href="mailto:Users@einsteintoolkit.org" target="_blank">Users@einsteintoolkit.org</a>
<a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" target="_blank">http://lists.einsteintoolkit.org/mailman/listinfo/users</a>
</pre>
</span></blockquote>
<br>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@einsteintoolkit.org" target="_blank">Users@einsteintoolkit.org</a><br>
<a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.einsteintoolkit.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>Users mailing list<br><a href="mailto:Users@einsteintoolkit.org" target="_blank">Users@einsteintoolkit.org</a><br><a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" target="_blank">http://lists.einsteintoolkit.org/mailman/listinfo/users</a><br></blockquote></div></div></div><span class="HOEnZb"><font color="#888888"><br><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div>-- </div><div>Ian Hinder</div><div><a href="http://members.aei.mpg.de/ianhin" target="_blank">http://members.aei.mpg.de/ianhin</a></div></div></div></div></div>
</div>
<br></font></span></div></blockquote></div><br></div>