Marco, can you please detail how you built Open MPI ?
i guess you downloaded a tarball and built from that. in this case, there is no need to run autogen.pl --force and unless something is wrong with the timestamps of the tarball, autoreconf should never be invoked. Cheers, Gilles On Sat, Sep 2, 2017 at 8:36 PM, Marco Atzeri <marco.atz...@gmail.com> wrote: > > > On 30/08/2017 22:48, Howard Pritchard wrote: >> >> Hi Folks, >> >> Open MPI 2.1.2rc3 tarballs are available for testing at the usual place: >> >> https://www.open-mpi.org/software/ompi/v2.1/ >> >> Fixes since rc2: >> >> Issue #4122: CMA compilation error in SM BTL. Thanks to Paul Hargrove >> for catching this. >> Issue #4034: NAG Fortran compiler -rpath configuration error. Thanks to >> Neil Carlson for >> reporting. >> >> Also, removed support for big endian PPC and XL compilers older than 13.1. >> >> Thanks, >> >> Jeff and Howard >> >> > > already seen on 2.1.1 > > autoreconf-2.69: running: aclocal --force -I config > sh: config/opal_get_version.sh: No such file or directory > sh: config/opal_get_version.sh: No such file or directory > > > I thought there was a file name mismatch > > $ file opal_get* > opal_get_version.m4: M4 macro processor script, ASCII text > opal_get_version.m4sh: ASCII text > > but it is not. > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
