Hi Freddie,
It appears that didn’t work—PyFR complains about being unable to find the
OpenMP header file. Looking at the compiler.py file in
${PYFR_ROOT}/pyfr/backends/openmp/ on line 55 you are using the value of cc to
get the path of the compiler to be used. Unfortunately, on OS X this is a
symbolic link to clang.
Is there an environment variable that PyFR supports that will allow you to
change which c compiler is used? Setting the shell environment variable CC is
ignored, so I was hoping there might be an alternative way to explicitly
specify the compiler PyFR uses. I have both gcc-4.9 (4.9.2) and have built an
OpenMP compatible version of clang which I’ve named clang-omp to test; however,
I can’t figure out how to direct PyFR to use those, rather than the cc symbolic
link (which points to clang bundled with Apple’s XCode command line tools).
Note, you also outlined an example of getting the copy of gcc-4.8 installed on
your mac to compile a simple Hello World example. I believe if you replaced the
-march=native option with something like -msse4.2 or -mtune=native, then the
code snippet compiles without the error. Although, I’m not certain that is
relevant to what you were pointing out.
Best Regards,
Zach
> On Nov 3, 2014, at 10:03 AM, Freddie Witherden <[email protected]> wrote:
>
> Hi Zach,
>
> On 03/11/14 17:35, Zach Davis wrote:
>> I have another follow-up question for you. I was able to confirm
>> that using the openmp backend, OS X was unable to compile the
>> requisite kernel due to lack of clang OpenMP support as you
>> mentioned. I found a post on stackoverflow referencing partial
>> OpenMP support in XCode 6 (clang 3.5) on OS X which can be activated
>> using the -Xclang -fopenmp=libiomp5 options
>> (http://stackoverflow.com/questions/26159225/openmp-support-in-xcode-6-clang-3-5).
>> The responder, Alexey Bataev, is doing this development work at Intel
>> I believe. Would passing these options to clang++ enable the kernel
>> to compile on OS X, or are we still left waiting for the OpenMP
>> implementation to be fully supported?
>
> I am unsure, but would be very interested to know if it fixes things or
> not. The command line arguments used by PyFR can be tweaked by
> modifying the list on:
>
> <https://github.com/VincentLab/PyFR/blob/develop/pyfr/backends/openmp/compiler.py#L69>
>
> and possibly also the command used to link the resulting object code
> together on line 79.
>
> Let me know if this gets things working or not.
>
> Regards, Freddie.
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyFR Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send an email to [email protected].
> Visit this group at http://groups.google.com/group/pyfrmailinglist.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "PyFR
Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send an email to [email protected].
Visit this group at http://groups.google.com/group/pyfrmailinglist.
For more options, visit https://groups.google.com/d/optout.
