<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 22 May 2015, at 16:10, Roberto De Pietri <<a href="mailto:roberto.depietri@unipr.it">roberto.depietri@unipr.it</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Ian:<br><br><br>Thanks for the answer. I followed exactly your procedure and I was very surprised of having<br>a failing compilation. Than I starting tracing back the problem. <br>* All the thorns except one were compiling correctly.<br>* The failing thorn was CarpetIOHDF5 and of the 5 source files present only 3 failed<br>* The error was very strange because the only real problem was related to <br> a system include “/opt/local/lib/gcc49/gcc/x86_64-apple-darwin14/4.9.2/include/mmintrin.h”<br> and was related to conversion using AVX intel intrinsic. The error were of the type:<br><br> error: can’t convert between vector values of different size<br> return (__m64) __builtin_ia32_vec_init_v2si (__i, 0);<br></blockquote><div><br></div><div>There is a stackoverflow post (<a href="http://stackoverflow.com/questions/19043109/gcc-4-8-1-combining-c-code-with-c11-code">http://stackoverflow.com/questions/19043109/gcc-4-8-1-combining-c-code-with-c11-code</a> ) which describes a similar problem, which I haven't studied in depth, but they seem to suggest that it's a bug in gcc, and that setting --std=gnu++11 instead of --std=c++11 in CXXFLAGS will work around the problem. We currently have</div><div><br></div><div><div><span class="Apple-tab-span" style="white-space:pre"> </span>CXXFLAGS = -g -std=c++14</div><div><br></div><div>so I'm guessing that changing this to</div><div><br></div><div><div><span class="Apple-tab-span" style="white-space:pre"> </span>CXXFLAGS = -g -std=gnu++14</div></div><div><br></div><div>might have the same effect.</div></div><div><br></div><div>What I don't understand is why we didn't pick this up in testing. I successfully compiled the whole ET using exactly that set of MacPorts packages and the optionlist before the release, and the gcc49 macports package hasn't been updated since 4 weeks ago.</div><div><br></div><div>When you say you followed exactly my procedure, do you mean that you get the above compilation problem even when you have only the ports listed in the optionlist installed, and have not installed anything else, such as gcc5 or the python packages? </div><div><br></div></div><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>-- </div><div>Ian Hinder</div><div><a href="http://members.aei.mpg.de/ianhin">http://members.aei.mpg.de/ianhin</a></div></div></div></div></div>
</div>
<br></body></html>