I figured it out.
In the real application, I also did not have the 'use' statement, and there
was an IMPLICIT statement causing the omp_get_max_threads() function to be
automatically compiled as a real function instead of as integer, and the
integers were automatically promoted to 8-byte using -i
I just built 1.7. If I distribute the binary, it works fine. If I use the
--preload-binary option, it prints
[warn] opal_libevent2019_event_base_loop: reentrant invocation. Only one
event_base_loop can run on each event_base at once.
many times per second.
I have bit of an odd configuration:
Unfortunately, that functionality fell into disrepair - it is scheduled to be
repaired/replaced in v1.7.2.
On Apr 9, 2013, at 4:30 PM, Thomas Vacek wrote:
> I just built 1.7. If I distribute the binary, it works fine. If I use the
> --preload-binary option, it prints
>
> [warn] opal_libeve
That answers that. Thanks for the help!
On 04/09/2013 08:04 PM, Ralph Castain wrote:
> Unfortunately, that functionality fell into disrepair - it is scheduled to be
> repaired/replaced in v1.7.2.
>
>
> On Apr 9, 2013, at 4:30 PM, Thomas Vacek wrote:
>
>> I just built 1.7. If I distribute the b
Hello,
thanks for the responses. But I have no idea how to do that. Which
environment variables should I look at? How do I find out where is the
openMPI installed and make the mpif90 use the openMPI?
Thanks,
Pradeep
2013/4/2 Elken, Tom
> > The Intel Fortran 2013 compiler comes with support fo
