Actually, the build is fine with this configure (as far as I have checked). I was just a bit skeptical because configure was generating an error instead of warning. Thank you for your help. Sahir
> On 28. Jun 2020, at 14:33, Jeff Squyres (jsquyres) via users > <users@lists.open-mpi.org> wrote: > > From the output you sent (directly to me / off-list), it looks like configure > finished properly. > > Are you running in to some kind of problem with building or running Open MPI? > > Remember: configure is probing / testing a zillion things on your system. > Many of the tests will fail (and they're supposed to). > > So unless you're actually running into a problem with building, installing, > or running Open MPI, I doubt this "objdump" warning is meaningful. > > > >> On Jun 28, 2020, at 7:58 AM, Sahir Butt <sahir.b...@rub.de >> <mailto:sahir.b...@rub.de>> wrote: >> >> For me also “which objdump” finds /usr/bin/objdump, don’t know why it goes >> for >> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump. >> Warnings and errors generated by running configure are: >> >> ../configure --prefix=/Users/sahirbutt/sw/opt/openmpi-4.0.3/ > stdout >> configure: WARNING: discovered external PMIx version is less than internal >> version 3.x >> configure: WARNING: using internal PMIx >> configure: WARNING: -fno-strict-aliasing has been added to CFLAGS >> configure: WARNING: -finline-functions has been added to CXXFLAGS >> configure: WARNING: -finline-functions has been added to CXXFLAGS >> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: >> error: 'conftest.o': Invalid/Unsupported object file format. >> configure: WARNING: *** Did not find corresponding C type >> configure: WARNING: Compiler INTEGER*16 and mismatch; MPI datatype >> unsupported >> configure: WARNING: "-fvisibility=hidden" has been added to the hwloc CFLAGS >> configure: WARNING: valgrind.h not found >> configure: WARNING: Cannot compile this component >> configure: WARNING: -fno-strict-aliasing has been added to CFLAGS >> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: >> error: 'conftest.o': Invalid/Unsupported object file format. >> configure: WARNING: Unknown architecture ... proceeding anyway >> configure: WARNING: File locks may not work with NFS. See the Installation >> and >> users manual for instructions on testing and if necessary fixing this >> >> Attached files are stdout and also config.log >> Thank you! >> Sahir >> -- >> >> >> >>> On 27. Jun 2020, at 17:48, Jeff Squyres (jsquyres) <jsquy...@cisco.com >>> <mailto:jsquy...@cisco.com>> wrote: >>> >>> On Jun 26, 2020, at 11:32 AM, Sahir Butt via users >>> <users@lists.open-mpi.org <mailto:users@lists.open-mpi.org>> wrote: >>>> >>>> I am trying to build openmpi-4.0.3 with gcc 11 on macOS. I ran following >>>> to configure: >>>> >>>> ../configure --prefix=/path-to/opt/openmpi-4.0.3 >>>> --with-wrapper-ldflags="-Wl,-search_paths_first” >>>> >>>> I keep getting following error: >>>> >>>> checking for objdump... objdump >>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: >>>> error: 'conftest.o': Invalid/Unsupported object file format. >>> >>> >>> This might mean that you have some kind of issue with your local compiler. >>> >>> FWIW, on my MacOS laptop, "which objdump" finds /usr/bin/objdump, not >>> /Applications/Xcode.app/...etc. >>> >>> Can you send the stdout/stderr from running configure, and the config.log >>> file? >>> >>> -- >>> Jeff Squyres >>> jsquy...@cisco.com <mailto:jsquy...@cisco.com> >>> >> >> <config.log><stdout> > > > -- > Jeff Squyres > jsquy...@cisco.com <mailto:jsquy...@cisco.com>
