<div dir="ltr">At least for my (newish) version of the Intel compilers, the flag "-fopenmp" is equivalent to "-openmp". Might want to try that instead.<div><br></div><div>-Zach</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Dec 10, 2013 at 12:57 PM, 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">
Yes. I hate intel for making their flag "-openmp".<br>
<br>
Cheers,<br>
Steve<br>
<div class="im HOEnZb"><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>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@einsteintoolkit.org">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>
</div></div></blockquote></div><br></div>