Jeff,

currently there is no way to retrieve the configure command line.

I previously discussed this with Jeff S. and it seems autotools do not
provide a reliable way to retrieve the configure command line.
I will have a look at how mpich is doing it, and try to mimick that in ompi.
if there is a consensus an approximation of the configure command line is
better than nothing, then I will push the changes.

Cheers,

Gilles

On Sunday, July 24, 2016, Jeff Hammond <jeff.scie...@gmail.com> wrote:

> ompi_info -h indicates that -c shows configuration options, ie configure
> arguments:
>
> $ /home/projects/x86-64-knl/openmpi/1.10.2/intel/17.0.042/bin/ompi_info -h
>
> --------------------------------------------------------------------------
>
> The ompi_info command can be used to provide detailed information on
>
> your Open MPI installation.  Syntax:
>
>
> -a|--all                 Show all configuration options and MCA parameters
>
>    -am <arg0>            Aggregate MCA parameter set file list
>
>    --arch                Show architecture Open MPI was compiled on
>
> -c|--config              Show configuration options
>
>
> So I expect something like what mpichversion gives me, which I find
> incredibly useful:
>
> $ ~/MPICH/install-ch3-ofi-psm2/bin/mpichversion
>
> MPICH Version:    3.2
>
> MPICH Release date: unreleased development copy
>
> MPICH Device:    ch3:nemesis
>
> MPICH configure: CC=icc CXX=icpc FC=ifort F77=ifort
> --with-ofi=~/OFI/install-psm2 --with-device=ch3:nemesis:ofi
> --prefix=~/MPICH/install-ch3-ofi-psm2
>
> MPICH CC: icc    -O2
>
> MPICH CXX: icpc   -O2
>
> MPICH F77: ifort   -O2
>
> MPICH FC: ifort   -O2
>
>
> Unfortunately, I see nothing that is directly convertible to configure
> arguments in the following:
>
> $ /home/projects/x86-64-knl/openmpi/1.10.2/intel/17.0.042/bin/ompi_info -c
>
>            Configured by: XXX
>
>            Configured on: Mon Apr 18 18:47:25 EDT 2016
>
>           Configure host: XXX
>
>                 Built by: XXX
>
>                 Built on: Mon Apr 18 19:16:55 EDT 2016
>
>               Built host: XXX
>
>               C bindings: yes
>
>             C++ bindings: yes
>
>              Fort mpif.h: yes (all)
>
>             Fort use mpi: yes (full: ignore TKR)
>
>        Fort use mpi size: deprecated-ompi-info-value
>
>         Fort use mpi_f08: yes
>
>  Fort mpi_f08 compliance: The mpi_f08 module is available, but due to
>
>                           limitations in the
>
>
> /home/projects/x86-64-knl/intel/compilers/2017-beta/compilers_and_libraries_2017.0.042/linux/bin/intel64/ifort
>
>                           compiler, does not support the following: array
>
>                           subsections, direct passthru (where possible) to
>
>                           underlying Open MPI's C functionality
>
>   Fort mpi_f08 subarrays: no
>
>            Java bindings: yes
>
>   Wrapper compiler rpath: runpath
>
>               C compiler:
> /home/projects/x86-64-knl/intel/compilers/2017-beta/compilers_and_libraries_2017.0.042/linux/bin/intel64/icc
>
>      C compiler absolute:
>
>   C compiler family name: INTEL
>
>       C compiler version: 1700.20160315
>
>              C char size: 1
>
>              C bool size: 1
>
>             C short size: 2
>
>               C int size: 4
>
>              C long size: 8
>
>             C float size: 4
>
>            C double size: 8
>
>           C pointer size: 8
>
>             C char align: 1
>
>             C bool align: 1
>
>              C int align: 4
>
>            C float align: 4
>
>           C double align: 8
>
>             C++ compiler:
> /home/projects/x86-64-knl/intel/compilers/2017-beta/compilers_and_libraries_2017.0.042/linux/bin/intel64/icpc
>
>    C++ compiler absolute: none
>
>            Fort compiler:
> /home/projects/x86-64-knl/intel/compilers/2017-beta/compilers_and_libraries_2017.0.042/linux/bin/intel64/ifort
>
>        Fort compiler abs:
>
>          Fort ignore TKR: yes (!DEC$ ATTRIBUTES NO_ARG_CHECK ::)
>
>    Fort 08 assumed shape: yes
>
>       Fort optional args: yes
>
>           Fort INTERFACE: yes
>
>     Fort ISO_FORTRAN_ENV: yes
>
>        Fort STORAGE_SIZE: yes
>
>       Fort BIND(C) (all): yes
>
>       Fort ISO_C_BINDING: yes
>
>  Fort SUBROUTINE BIND(C): yes
>
>        Fort TYPE,BIND(C): yes
>
>  Fort T,BIND(C,name="a"): yes
>
>             Fort PRIVATE: yes
>
>           Fort PROTECTED: yes
>
>            Fort ABSTRACT: yes
>
>        Fort ASYNCHRONOUS: yes
>
>           Fort PROCEDURE: yes
>
>          Fort USE...ONLY: yes
>
>            Fort C_FUNLOC: yes
>
>  Fort f08 using wrappers: yes
>
>          Fort MPI_SIZEOF: yes
>
>        Fort integer size: 4
>
>        Fort logical size: 4
>
>  Fort logical value true: -1
>
>       Fort have integer1: yes
>
>       Fort have integer2: yes
>
>       Fort have integer4: yes
>
>       Fort have integer8: yes
>
>      Fort have integer16: no
>
>          Fort have real4: yes
>
>          Fort have real8: yes
>
>         Fort have real16: yes
>
>       Fort have complex8: yes
>
>      Fort have complex16: yes
>
>      Fort have complex32: yes
>
>       Fort integer1 size: 1
>
>       Fort integer2 size: 2
>
>       Fort integer4 size: 4
>
>       Fort integer8 size: 8
>
>      Fort integer16 size: -1
>
>           Fort real size: 4
>
>          Fort real4 size: 4
>
>          Fort real8 size: 8
>
>         Fort real16 size: 16
>
>       Fort dbl prec size: 8
>
>           Fort cplx size: 8
>
>       Fort dbl cplx size: 16
>
>          Fort cplx8 size: 8
>
>         Fort cplx16 size: 16
>
>         Fort cplx32 size: 32
>
>       Fort integer align: 1
>
>      Fort integer1 align: 1
>
>      Fort integer2 align: 1
>
>      Fort integer4 align: 1
>
>      Fort integer8 align: 1
>
>     Fort integer16 align: -1
>
>          Fort real align: 1
>
>         Fort real4 align: 1
>
>         Fort real8 align: 1
>
>        Fort real16 align: 1
>
>      Fort dbl prec align: 1
>
>          Fort cplx align: 1
>
>      Fort dbl cplx align: 1
>
>         Fort cplx8 align: 1
>
>        Fort cplx16 align: 1
>
>        Fort cplx32 align: 1
>
>              C profiling: yes
>
>            C++ profiling: yes
>
>    Fort mpif.h profiling: yes
>
>   Fort use mpi profiling: yes
>
>    Fort use mpi_f08 prof: yes
>
>           C++ exceptions: no
>
>           Thread support: posix (MPI_THREAD_MULTIPLE: yes, OPAL support:
> yes,
>
>                           OMPI progress: no, ORTE progress: yes, Event lib:
>
>                           yes)
>
>            Sparse Groups: no
>
>             Build CFLAGS: -O3 -DNDEBUG -finline-functions
>
>                           -fno-strict-aliasing -restrict
>
>                           -Qoption,cpp,--extended_float_types -pthread
>
>           Build CXXFLAGS: -O3 -DNDEBUG -finline-functions -pthread
>
>            Build FCFLAGS:
>
>            Build LDFLAGS: -L/home/projects/x86-64-knl/hwloc/1.11.3/lib
>
>               Build LIBS: -lrt -lutil   -lhwloc
>
>     Wrapper extra CFLAGS: -pthread
>
>   Wrapper extra CXXFLAGS: -pthread
>
>    Wrapper extra FCFLAGS:
>
>    Wrapper extra LDFLAGS: -Wl,-rpath -Wl,@{libdir} -Wl,--enable-new-dtags
>
>       Wrapper extra LIBS: -ldl -lutil
>
>   Internal debug support: no
>
>   MPI interface warnings: yes
>
>      MPI parameter check: runtime
>
> Memory profiling support: no
>
> Memory debugging support: no
>
>               dl support: yes
>
>    Heterogeneous support: no
>
>  mpirun default --prefix: no
>
>          MPI I/O support: yes
>
>        MPI_WTIME support: gettimeofday
>
>      Symbol vis. support: yes
>
>    Host topology support: yes
>
>           MPI extensions:
>
>    FT Checkpoint support: no (checkpoint thread: no)
>
>    C/R Enabled Debugging: no
>
>      VampirTrace support: yes
>
>   MPI_MAX_PROCESSOR_NAME: 256
>
>     MPI_MAX_ERROR_STRING: 256
>
>      MPI_MAX_OBJECT_NAME: 64
>
>         MPI_MAX_INFO_KEY: 36
>
>         MPI_MAX_INFO_VAL: 256
>
>        MPI_MAX_PORT_NAME: 1024
>
>   MPI_MAX_DATAREP_STRING: 128
>
> How do I extract configure arguments from an OpenMPI installation?  I am
> trying to reproduce a build exactly and I do not have access to config.log
> from the origin build.
>
> Thanks,
>
> Jeff
>
> --
> Jeff Hammond
> jeff.scie...@gmail.com
> <javascript:_e(%7B%7D,'cvml','jeff.scie...@gmail.com');>
> http://jeffhammond.github.io/
>

Reply via email to