Re: [OMPI users] OpenMPI 2.1.0: FAIL: opal_path_nfs

2017-04-26 Thread r...@open-mpi.org
We have a utility that checks to ensure that the shared memory backing file is not on a shared file system. The test is checking to see if that utility can stat and assess the nature of any file system on your node. It’s undoubtedly stale as things have changed over the years (new file systems

Re: [OMPI users] OpenMPI 2.1.0: FAIL: opal_path_nfs

2017-04-26 Thread Prentice Bisbal
That's what I figured, but I wanted to check first. Any idea of exactly what it's trying to check? Prentice On 04/26/2017 05:54 PM, r...@open-mpi.org wrote: You can probably safely ignore it. On Apr 26, 2017, at 2:29 PM, Prentice Bisbal wrote: I'm trying to build OpenMPI

Re: [OMPI users] OpenMPI 2.1.0: FAIL: opal_path_nfs

2017-04-26 Thread r...@open-mpi.org
You can probably safely ignore it. > On Apr 26, 2017, at 2:29 PM, Prentice Bisbal wrote: > > I'm trying to build OpenMPI 2.1.0 with GCC 5.4.0 on CentOS 6.8. After working > around the '-Lyes/lib' errors I reported in my previous post, opal_path_nfs > fails during 'make

[OMPI users] OpenMPI 2.1.0: FAIL: opal_path_nfs

2017-04-26 Thread Prentice Bisbal
I'm trying to build OpenMPI 2.1.0 with GCC 5.4.0 on CentOS 6.8. After working around the '-Lyes/lib' errors I reported in my previous post, opal_path_nfs fails during 'make check' (see below). Is this failure critical, or is it something I can ignore and continue with my install? Googling only