[OMPI users] Problem building OpenMPI 1.8 on RHEL6
I am getting some errors building 1.8 on RHEL6. I tried autoreconf as suggested, but it failed for the same reason. Is there a minimum version of m4 required that is newer than that provided by RHEL6? Thanks aclocal.m4:16: warning: this file was generated for autoconf 2.69. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically 'autoreconf'. configure.ac:40: error: m4_defn: undefined macro: _m4_divert_diversion configure.ac:40: the top level autom4te: /usr/bin/m4 failed with exit status: 1 [bloscel@head openmpi]$ autoreconf configure.ac:40: error: m4_defn: undefined macro: _m4_divert_diversion configure.ac:40: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1
Re: [OMPI users] Problem building OpenMPI 1.8 on RHEL6
Hmmm...indeed, it looks like the default versions may be out-of-date. Here is a table showing the required rev levels: http://www.open-mpi.org/svn/building.php On Apr 1, 2014, at 8:26 AM, Blosch, Edwin L wrote: > I am getting some errors building 1.8 on RHEL6. I tried autoreconf as > suggested, but it failed for the same reason. Is there a minimum version of > m4 required that is newer than that provided by RHEL6? > > Thanks > > aclocal.m4:16: warning: this file was generated for autoconf 2.69. > You have another version of autoconf. It may work, but is not guaranteed to. > If you have problems, you may need to regenerate the build system entirely. > To do so, use the procedure documented by the package, typically 'autoreconf'. > configure.ac:40: error: m4_defn: undefined macro: _m4_divert_diversion > configure.ac:40: the top level > autom4te: /usr/bin/m4 failed with exit status: 1 > > [bloscel@head openmpi]$ autoreconf > configure.ac:40: error: m4_defn: undefined macro: _m4_divert_diversion > configure.ac:40: the top level > autom4te: /usr/bin/m4 failed with exit status: 1 > aclocal: autom4te failed with exit status: 1 > autoreconf: aclocal failed with exit status: 1 > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Problem building OpenMPI 1.8 on RHEL6
On Apr 1, 2014, at 10:26 AM, "Blosch, Edwin L" wrote: > I am getting some errors building 1.8 on RHEL6. I tried autoreconf as > suggested, but it failed for the same reason. Is there a minimum version of > m4 required that is newer than that provided by RHEL6? Don't run "autoreconf" by hand, make sure to run the "./autogen.sh" script that is packaged with OMPI. It will also check your versions and warn you if they are out of date. Do you need to build OMPI from the SVN source? Or would a (pre-autogen'ed) release tarball work for you? -Dave
Re: [OMPI users] usNIC point-to-point messaging module
Dear Ralph, Dear Jeff, I've just recompiled the latest Open MPI 1.8. I added "--enable-mca-no-build=btl-usnic" to configure but the message still appear. Here the output of "--mca btl_base_verbose 100" (trunked immediately after the application starts) srun: cluster configuration lacks support for cpu binding [tesla88:26769] mca: base: components_register: registering btl components [tesla88:26769] mca: base: components_register: found loaded component openib [tesla88:26768] mca: base: components_register: registering btl components [tesla88:26768] mca: base: components_register: found loaded component openib [tesla88:26768] mca: base: components_register: component openib register function successful [tesla88:26769] mca: base: components_register: component openib register function successful [tesla88:26769] mca: base: components_register: found loaded component self [tesla88:26768] mca: base: components_register: found loaded component self [tesla88:26769] mca: base: components_register: component self register function successful [tesla88:26768] mca: base: components_register: component self register function successful [tesla88:26769] mca: base: components_register: found loaded component sm [tesla88:26768] mca: base: components_register: found loaded component sm [tesla88:26769] mca: base: components_register: component sm register function successful [tesla88:26768] mca: base: components_register: component sm register function successful [tesla88:26769] mca: base: components_register: found loaded component tcp [tesla88:26768] mca: base: components_register: found loaded component tcp [tesla88:26769] mca: base: components_register: component tcp register function successful [tesla88:26768] mca: base: components_register: component tcp register function successful [tesla88:26769] mca: base: components_register: found loaded component usnic [tesla88:26768] mca: base: components_register: found loaded component usnic [tesla88:26769] mca: base: components_register: component usnic register function successful [tesla88:26768] mca: base: components_register: component usnic register function successful [tesla88:26769] mca: base: components_register: found loaded component vader [tesla88:26768] mca: base: components_register: found loaded component vader [tesla88:26769] mca: base: components_register: component vader register function successful [tesla88:26769] mca: base: components_open: opening btl components [tesla88:26769] mca: base: components_open: found loaded component openib [tesla88:26769] mca: base: components_open: component openib open function successful [tesla88:26769] mca: base: components_open: found loaded component self [tesla88:26768] mca: base: components_register: component vader register function successful [tesla88:26769] mca: base: components_open: component self open function successful [tesla88:26769] mca: base: components_open: found loaded component sm [tesla88:26769] mca: base: components_open: component sm open function successful [tesla88:26769] mca: base: components_open: found loaded component tcp [tesla88:26768] mca: base: components_open: opening btl components [tesla88:26768] mca: base: components_open: found loaded component openib [tesla88:26768] mca: base: components_open: component openib open function successful [tesla88:26768] mca: base: components_open: found loaded component self [tesla88:26768] mca: base: components_open: component self open function successful [tesla88:26768] mca: base: components_open: found loaded component sm [tesla88:26768] mca: base: components_open: component sm open function successful [tesla88:26768] mca: base: components_open: found loaded component tcp [tesla88:26769] mca: base: components_open: component tcp open function successful [tesla88:26769] mca: base: components_open: found loaded component usnic [tesla88:26769] mca: base: components_open: component usnic open function successful [tesla88:26769] mca: base: components_open: found loaded component vader [tesla88:26769] mca: base: components_open: component vader open function successful [tesla89:45456] mca: base: components_register: registering btl components [tesla89:45456] mca: base: components_register: found loaded component openib [tesla88:26768] mca: base: components_open: component tcp open function successful [tesla88:26768] mca: base: components_open: found loaded component usnic [tesla88:26768] mca: base: components_open: component usnic open function successful [tesla88:26768] mca: base: components_open: found loaded component vader [tesla88:26768] mca: base: components_open: component vader open function successful [tesla89:45455] mca: base: components_register: registering btl components [tesla89:45455] mca: base: components_register: found loaded component openib [tesla89:45456] mca: base: components_register: component openib register function successful [tesla89:45456] mca: base: components_register: found loaded component self [
Re: [OMPI users] usNIC point-to-point messaging module
On Apr 1, 2014, at 12:13 PM, Filippo Spiga wrote: > Dear Ralph, Dear Jeff, > > I've just recompiled the latest Open MPI 1.8. I added > "--enable-mca-no-build=btl-usnic" to configure but the message still appear. > Here the output of "--mca btl_base_verbose 100" (trunked immediately after > the application starts) Jeff's on vacation, so I'll see if I can help here. Try deleting all the files in "$PREFIX/lib/openmpi/", where "$PREFIX" is the value you passed to configure with "--prefix=". If you did not pass a value, then it is "/usr/local". Then reinstall (with "make install" in the OMPI build tree). What I think is happening is that you still have an "mca_btl_usnic.so" file leftover from the last time you installed OMPI (before passing "--enable-mca-no-build=btl-usnic"). So OMPI is using this shared library and you get exactly the same problem. -Dave
Re: [OMPI users] Issue with QLogic IBA7322 QDR InfiniBand HCA
Em 31-03-2014 23:06, Fabricio Cannini escreveu: Problem solved. Rocks wasn't correctly generating '/etc/hosts' when the node was installed. [ ]'s
