Comer
I agree with you that the PAPI errors seem harmless.
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.
This is quite annoying, since several of us tested this option list, and it worked for all of us...
Can you send us the output of
g++-mp-4.9 --version
and
/opt/local/bin/mpicxx --version
?
-erik
On Thu, May 21, 2015 at 2:44 PM, Comer Duncan comer.duncan@gmail.com wrote:
HI Frank,
I am running 10.10.3 (14D136) on a macbook pro with the following properties:
Version 10.10.3 (14D136) MacBook Pro (Retina, 15-inch, Mid 2014) Processor 2.5 Ghz Intel Core i7 (4 cores) 16 GB with 1TB SSD
I am up to date with macports (I do this every week or so).
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?
Please help.
Thanks.
Comer
On Thu, May 21, 2015 at 2:30 PM, Frank Loeffler knarf@cct.lsu.edu wrote:
On Thu, May 21, 2015 at 01:52:25PM -0400, Comer Duncan wrote:
I have rebuilt Hilbert using the new detect.pl file suggested and get a make crash but this time referring to seemingly different compile
problems.
I have pasted the build4.log file to http://pastebin.com/kECKTkqr
Which Mac OS version do you have again? Could it be connected to this?
http://stackoverflow.com/questions/15963277/performance-api-on-mac-10-8
(there is no solution given there, but the symptoms fit)
Frank