<div dir="ltr">That's a very good point. I'm curious, does <span style="font-family:arial,sans-serif;font-size:13px">CPP_OPENMP_FLAGS need to be set for any compiler? I've never set it, and have run successfully with OpenMP using pretty much every major compiler out there (albeit with older versions of ET).</span>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 10, 2013 at 1:40 PM, Yosef Zlochower <span dir="ltr"><<a href="mailto:yosef@astro.rit.edu" target="_blank">yosef@astro.rit.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Aren't these options for icc. Does cpp even need<br>
-openmp under intel?<div><br>
<br>
On 12/10/2013 01:26 PM, Zach Etienne wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
At least for my (newish) version of the Intel compilers, the flag<br>
"-fopenmp" is equivalent to "-openmp". Might want to try that instead.<br>
<br>
-Zach<br>
<br>
<br>
On Tue, Dec 10, 2013 at 12:57 PM, Steven R. Brandt <<a href="mailto:sbrandt@cct.lsu.edu" target="_blank">sbrandt@cct.lsu.edu</a><br></div><div>
<mailto:<a href="mailto:sbrandt@cct.lsu.edu" target="_blank">sbrandt@cct.lsu.edu</a>>> wrote:<br>
<br>
Yes. I hate intel for making their flag "-openmp".<br>
<br>
Cheers,<br>
Steve<br>
<br>
On 12/10/2013 10:33 AM, Yosef Zlochower wrote:<br>
> Hi,<br>
><br>
> Every now and then I rediscover a bug that I make when I use<br>
> one of the simfactory option files as a starting point for<br>
> our local cluster. Since our local cluster is similar to<br>
> Lonestar, I start from one of the Lonestar configuration<br>
><br>
> Howerver, the option<br>
> " CPP_OPENMP_FLAGS = -openmp"<br>
> Leads to failed compiles because<br>
> cpp -openmp BLAH causes the output of cpp to go to a file<br>
> called penmp rather than stdout.<br>
> I just wonder if other people were bitten by this.<br>
><br>
> On Noether, this caused the compile of GSL to fail<br>
> (btw, only GSL, the rest of ET compiled fine).<br>
><br>
><br>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br></div>
<a href="mailto:Users@einsteintoolkit.org" target="_blank">Users@einsteintoolkit.org</a> <mailto:<a href="mailto:Users@einsteintoolkit.org" target="_blank">Users@einsteintoolkit.<u></u>org</a>><br>
<a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" target="_blank">http://lists.einsteintoolkit.<u></u>org/mailman/listinfo/users</a><div><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<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.<u></u>org/mailman/listinfo/users</a><br>
<br>
</div></blockquote>
<br><div><div>
<br>
-- <br>
Dr. Yosef Zlochower<br>
Center for Computational Relativity and Gravitation<br>
Associate Professor<br>
School of Mathematical Sciences<br>
Rochester Institute of Technology<br>
85 Lomb Memorial Drive<br>
Rochester, NY 14623<br>
<br>
Office:74-2067<br>
Phone: <a href="tel:%2B1%20585-475-6103" value="+15854756103" target="_blank">+1 585-475-6103</a><br>
<br>
<a href="mailto:yosef@astro.rit.edu" target="_blank">yosef@astro.rit.edu</a><br>
<br>
CONFIDENTIALITY NOTE: The information transmitted, including<br>
attachments, is intended only for the person(s) or entity to which it<br>
is addressed and may contain confidential and/or privileged material.<br>
Any review, retransmission, dissemination or other use of, or taking<br>
of any action in reliance upon this information by persons or entities<br>
other than the intended recipient is prohibited. If you received this<br>
in error, please contact the sender and destroy any copies of this<br>
information.<br>
</div></div></blockquote></div><br></div></div>