<div dir="ltr">Erik,<div><br></div><div>Sure. Here you go.</div><div><br></div><div><div>ComerMacProRetina:Cactus comerduncan$ g++-mp-4.9 --version</div><div>g++-mp-4.9 (MacPorts gcc49 4.9.2_1) 4.9.2</div><div>Copyright (C) 2014 Free Software Foundation, Inc.</div><div>This is free software; see the source for copying conditions. There is NO</div><div>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</div></div><div><br></div><div>and</div><div><br></div><div><div>ComerMacProRetina:Cactus comerduncan$ /opt/local/bin/mpicxx --version</div><div>Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn)</div><div>Target: x86_64-apple-darwin14.3.0</div><div>Thread model: posix</div></div><div><br></div><div>I just did my usual macports maintenance script yesterday:</div><div><br></div><div><div>ComerMacProRetina:bin comerduncan$ cat portupdateupgrade</div><div>echo '------------selfupdate------------------'</div><div>sudo port selfupdate</div><div>echo '------------outdated ports--------------'</div><div>sudo port outdated</div><div>echo '------------upgrade outdated ports------'</div><div>sudo port upgrade outdated</div></div><div><br></div><div>Has macports stuff been polluted? I note that on May 20 the software update for mac osx included installed updates of Xcode to version 6.3.2 and Command Line Tools version 6.3. I am wondering whether the attempts at building Cactus intersected macports updates performed with updated Xcode/Command LIne Tools, so that the macport collection might be in somewhat of a conflicted state?</div><div><br></div><div>Comer</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 21, 2015 at 3:16 PM, Erik Schnetter <span dir="ltr"><<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@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 dir="ltr">Comer<div><br></div><div>I agree with you that the PAPI errors seem harmless.</div><div><br></div><div>The problem seems to be that something is wrong with vectorization. The error is reported inside a compiler-provided file. I don't know why these errors would now suddenly appear, as they were not there before. It looks as if something related to the C++ compiler changed.</div><div><br></div><div>This is quite annoying, since several of us tested this option list, and it worked for all of us...</div><div><br></div><div>Can you send us the output of</div><div><br></div><div>g++-mp-4.9 --version</div><div><br></div><div>and</div><div><br></div><div>/opt/local/bin/mpicxx --version</div><div><br></div><div>?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-erik</div><div><br></div></font></span></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Thu, May 21, 2015 at 2:44 PM, Comer Duncan <span dir="ltr"><<a href="mailto:comer.duncan@gmail.com" target="_blank">comer.duncan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">HI Frank,<div><br></div><div>I am running 10.10.3 (14D136) on a macbook pro with the following properties:</div><div><br></div><div>Version 10.10.3 (14D136)<br></div><div>MacBook Pro (Retina, 15-inch, Mid 2014)<br></div><div>Processor 2.5 Ghz Intel Core i7 (4 cores)</div><div>16 GB with 1TB SSD</div><div><br></div><div>I am up to date with macports (I do this every week or so).</div><div><br></div><div>I noticed complaints about papi but since builds don't crash with such complaints I forged ahead. I also note in the build logs multiple mentions (1405!) of Nonexistent include directories. How come such warnings are there in a new release? Maybe unrelated or not worth worrying about? </div><div><br></div><div>Please help.</div><div><br></div><div>Thanks.</div><span><font color="#888888"><div><br></div><div>Comer</div><div><br></div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 21, 2015 at 2:30 PM, Frank Loeffler <span dir="ltr"><<a href="mailto:knarf@cct.lsu.edu" target="_blank">knarf@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"><span>On Thu, May 21, 2015 at 01:52:25PM -0400, Comer Duncan wrote:<br>
> I have rebuilt Hilbert using the new <a href="http://detect.pl" target="_blank">detect.pl</a> file suggested and get a<br>
> make crash but this time referring to seemingly different compile problems.<br>
> I have pasted the build4.log file to <a href="http://pastebin.com/kECKTkqr" target="_blank">http://pastebin.com/kECKTkqr</a><br>
<br>
</span>Which Mac OS version do you have again? Could it be connected to this?<br>
<br>
<a href="http://stackoverflow.com/questions/15963277/performance-api-on-mac-10-8" target="_blank">http://stackoverflow.com/questions/15963277/performance-api-on-mac-10-8</a><br>
<br>
(there is no solution given there, but the symptoms fit)<br>
<span><font color="#888888"><br>
Frank<br>
<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="">-- <br><div>Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>><br><a href="http://www.perimeterinstitute.ca/personal/eschnetter/" target="_blank">http://www.perimeterinstitute.ca/personal/eschnetter/</a></div>
</span></div>
</blockquote></div><br></div>