Hi Freddie,
Do you have any suggestion how to do it?
I tried cc = icl (intel c compiler code for windows corresponding to icc of
linux)
I tried cc = full path\icl.exe
I tried to launch pyfr from Intel compiler command window.
Each time I get this error:
The first part with OpenMp Kernel
Hi Emre,
On 11/04/2016 07:42, emre wrote:
> I am sorry I could not thank you sooner, for your reply. Unfortunately I
> could not do what you suggested "run a C code with the arguments given
> in the error". I do not know C. But I worked on python installation
> thinking that it might be related
Hi Emre,
On 31/03/2016 17:24, emre wrote:
> I have a similar problem.
>
> I installed Anaconda distribution, therefore I am not sure about the
> compiler but mpi4py seems to work only with Intel MPI. At first it was
> installing using MS MPI with wrong directories, then I corrected them
> with
Hi Freddie,
I have a similar problem.
I installed Anaconda distribution, therefore I am not sure about the
compiler but mpi4py seems to work only with Intel MPI. At first it was
installing using MS MPI with wrong directories, then I corrected them with
correct MS MPI. But the result of
Hi Freddie,
After commenting out the prefork enabling, I made the following changes to
util.py on the call function, from line 21.
def __call__(self, *args, **kwargs):
instance = args[0]
print("")
print(self)
print("--self")
print(*args)
Hi Leo,
On 24/02/16 16:17, 'Leo Allen' via PyFR Mailing List wrote:
> Hello, I've been using PyFR on a windows laptop with Cygwin 64bit, and
> after upgrading pyfr to 1.3, I get an error which seems to persist even
> when I downgrade back to 1.2.
Nothing substantial changed between v1.2.0 and