On 12/17/2014 07:04 PM, Eric Chamberland wrote:
Hi!
Here is a "poor man's fix" that works for me (the idea is not from me,
thanks to Thomas H.):
#1- char* lCwd = getcwd(0,0);
#2- chdir(lPathToFile);
#3- MPI_File_open(...,lFileNameWithoutTooLongPath,...);
#4- chdir(lCwd);
#5- ...
I think
It's worth noting that the solution solved the problem.
I'm running on RHEL5, which seems like it's actually where the problem comes
from.
--
*Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
|| \\UTGERS |-*O*-
||_// Biomedical |
Gilles,
The issue you pointed Ryan to was with GCC 4.8.2 not 4.9.2. I just
built version 1.8.4 on a RHEL6 machine yesterday without special
switches but with GCC 4.9.2.
Ray
On 1/14/2015 11:13 AM, Novosielski, Ryan wrote:
Thank you. I did a search, but somehow did not
Thank you. I did a search, but somehow did not turn that up. I guess I had
looked for GCC 4.9.
*Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
|| \\UTGERS |-*O*-
||_// Biomedical | Ryan Novosielski - Senior Technologist
|| \\ and
Have you turned on valgrind support in Open MPI. That is required to
quite these bogus warnings.
-Nathan
On Wed, Jan 14, 2015 at 10:17:50AM +, Victor Vysotskiy wrote:
> Hi,
>
> Our parallel applications behaves strange when it is compiled with Openmpi
> v1.8.4 on both Linux and Mac OS X
Hi,
Our parallel applications behaves strange when it is compiled with Openmpi
v1.8.4 on both Linux and Mac OS X platforms. The Valgrind reports memory
problems in OpenMPI rather than in our code:
=4440== Invalid read of size 1
==4440==at 0xCAD6D37: ompi_osc_rdma_callback
Ryan,
this issue has already been reported.
please refer to
http://www.open-mpi.org/community/lists/users/2015/01/26134.php for a
workaround
Cheers,
Gilles
On 2015/01/14 16:35, Novosielski, Ryan wrote:
> OpenMPI 1.8.4 does not appear to be buildable with GCC 4.9.2. The output, as
> requested
OpenMPI 1.8.4 does not appear to be buildable with GCC 4.9.2. The output, as
requested by the Getting Help page, is attached.
I believe I tried GCC 4.9.0 too and it didn't work.
I did successfully build it with Intel's compiler suite v15.0.1, so I do appear
to know what I'm doing.
Thanks in
