Re: [OMPI users] OpenMPI building fails on Windows Linux Subsystem(WLS).
Oleg, I can build the latest master branch of OpenMPI in WSL I can give it a try with 3.1.2 if that is any help to you? uname -a Linux Johns-Spectre 4.4.0-17134-Microsoft #285-Microsoft Thu Aug 30 17:31:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux apt-get upgrade apt-get install gfortran wget https://github.com/open-mpi/ompi/archive/master.zip cd ompi-master ./autogen.pl ./configure --enable-mpi-cxx make -j 2 configure returns this: Open MPI configuration: --- Version: 4.1.0a1 Build MPI C bindings: yes Build MPI C++ bindings (deprecated): yes Build MPI Fortran bindings: mpif.h, use mpi, use mpi_f08 MPI Build Java bindings (experimental): no Build Open SHMEM support: false (no spml) Debug build: no Platform file: (none) Miscellaneous --- CUDA support: no HWLOC support: internal Libevent support: internal PMIx support: internal Transports --- Cisco usNIC: no Cray uGNI (Gemini/Aries): no Intel Omnipath (PSM2): no Intel TrueScale (PSM): no Mellanox MXM: no Open UCX: no OpenFabrics Libfabric: no OpenFabrics Verbs: no Portals4: no Shared memory/copy in+copy out: yes Shared memory/Linux CMA: yes Shared memory/Linux KNEM: no Shared memory/XPMEM: no TCP: yes Resource Managers --- Cray Alps: no Grid Engine: no LSF: no Moab: no Slurm: yes ssh/rsh: yes Torque: no OMPIO File Systems --- DDN Infinite Memory Engine: no Generic Unix FS: yes Lustre: no PVFS2/OrangeFS: no On Wed, 19 Sep 2018 at 17:36, John Hearns wrote: > > Oleg, I have a Windows 10 system and could help by testing this also. > But I have to say - it will be quicker just to install VirtualBox and > a CentOS VM. Or an Ubuntu VM. > You can then set up a small test network of VMs using the VirtualBox > HostOnly network for tests of your MPI code. > On Wed, 19 Sep 2018 at 16:59, Jeff Squyres (jsquyres) via users > wrote: > > > > I can't say that we've tried to build on WSL; the fact that it fails is > > probably not entirely unsurprising. :-( > > > > I looked at your logs, and although I see the compile failure, I don't see > > any reason *why* it failed. Here's the relevant fail from the > > tar_openmpi_fail file: > > > > - > > 5523 Making all in mca/filem > > 5524 make[2]: Entering directory > > '/mnt/c/Users/ofcra/dev/openmpi-3.1.2/orte/mca/filem' > > 5525 GENERATE orte_filem.7 > > 5526 CC base/filem_base_frame.lo > > 5527 CC base/filem_base_select.lo > > 5528 CC base/filem_base_receive.lo > > 5529 CC base/filem_base_fns.lo > > 5530 base/filem_base_receive.c: In function > > ‘filem_base_process_get_remote_path_cmd’: > > 5531 base/filem_base_receive.c:250:9: warning: ignoring return value of > > ‘getcwd’, declared with attribute warn_unused_result [-Wunused-result] > > 5532 getcwd(cwd, sizeof(cwd)); > > 5533 ^~~~ > > 5534 base/filem_base_receive.c:251:9: warning: ignoring return value of > > ‘asprintf’, declared with attribute warn_unused_result [-Wunused-result] > > 5535 asprintf(_name, "%s/%s", cwd, filename); > > 5536 ^~~ > > 5537 Makefile:1892: recipe for target 'base/filem_base_select.lo' failed > > 5538 make[2]: *** [base/filem_base_select.lo] Error 1 > > 5539 make[2]: *** Waiting for unfinished jobs > > 5540 make[2]: Leaving directory > > '/mnt/c/Users/ofcra/dev/openmpi-3.1.2/orte/mca/filem' > > 5541 Makefile:2586: recipe for target 'all-recursive' failed > > 5542 make[1]: *** [all-recursive] Error 1 > > 5543 make[1]: Leaving directory '/mnt/c/Users/ofcra/dev/openmpi-3.1.2/orte' > > 5544 Makefile:1897: recipe for target 'all-recursive' failed > > 5545 make: *** [all-recursive] Error 1 > > - > > > > I.e., I see "recipe for target 'base/filem_base_select.lo' failed" -- but > > there's no error indicating *why* it failed. There were 2 warnings when > > compiling that file -- but not errors. That should not have prevented > > compilation for that .c file. > > > > You then went on to run "make check", but that failed predictably because > > "make" had already failed. > > > > You might want to run "make V=1" to see if you can get more details about > > why orte/mca/filem/base/filem_base_select.c failed to compile properly. > > > > It looks like your GitHub clone build failed in exactly the same place. > > > > There's something about filem_base_select.c that is failing to compile -- > > that's what we need more detail on. > > > > > > > > > On Sep 18, 2018, at 10:06 AM, Oleg Kmechak wrote: > > > > > > Hello, > > > > > > I am student of Physics from University of Warsaw, and new to OpenMPI. > > > Currently just trying to compile it from source code(tried both github > > > and tar(3.1.2)). > > > I am using Windows Linux Subsystem(WLS), Ubuntu. > > > > > > uname -a: > > > >Linux Canopus 4.4.0-17134-Microsoft #285-Microsoft Thu Aug 30 17:31:00 > > > >PST 2018 x86_64 x86_64 x86_64
Re: [OMPI users] OpenMPI building fails on Windows Linux Subsystem(WLS).
Oleg, I have a Windows 10 system and could help by testing this also. But I have to say - it will be quicker just to install VirtualBox and a CentOS VM. Or an Ubuntu VM. You can then set up a small test network of VMs using the VirtualBox HostOnly network for tests of your MPI code. On Wed, 19 Sep 2018 at 16:59, Jeff Squyres (jsquyres) via users wrote: > > I can't say that we've tried to build on WSL; the fact that it fails is > probably not entirely unsurprising. :-( > > I looked at your logs, and although I see the compile failure, I don't see > any reason *why* it failed. Here's the relevant fail from the > tar_openmpi_fail file: > > - > 5523 Making all in mca/filem > 5524 make[2]: Entering directory > '/mnt/c/Users/ofcra/dev/openmpi-3.1.2/orte/mca/filem' > 5525 GENERATE orte_filem.7 > 5526 CC base/filem_base_frame.lo > 5527 CC base/filem_base_select.lo > 5528 CC base/filem_base_receive.lo > 5529 CC base/filem_base_fns.lo > 5530 base/filem_base_receive.c: In function > ‘filem_base_process_get_remote_path_cmd’: > 5531 base/filem_base_receive.c:250:9: warning: ignoring return value of > ‘getcwd’, declared with attribute warn_unused_result [-Wunused-result] > 5532 getcwd(cwd, sizeof(cwd)); > 5533 ^~~~ > 5534 base/filem_base_receive.c:251:9: warning: ignoring return value of > ‘asprintf’, declared with attribute warn_unused_result [-Wunused-result] > 5535 asprintf(_name, "%s/%s", cwd, filename); > 5536 ^~~ > 5537 Makefile:1892: recipe for target 'base/filem_base_select.lo' failed > 5538 make[2]: *** [base/filem_base_select.lo] Error 1 > 5539 make[2]: *** Waiting for unfinished jobs > 5540 make[2]: Leaving directory > '/mnt/c/Users/ofcra/dev/openmpi-3.1.2/orte/mca/filem' > 5541 Makefile:2586: recipe for target 'all-recursive' failed > 5542 make[1]: *** [all-recursive] Error 1 > 5543 make[1]: Leaving directory '/mnt/c/Users/ofcra/dev/openmpi-3.1.2/orte' > 5544 Makefile:1897: recipe for target 'all-recursive' failed > 5545 make: *** [all-recursive] Error 1 > - > > I.e., I see "recipe for target 'base/filem_base_select.lo' failed" -- but > there's no error indicating *why* it failed. There were 2 warnings when > compiling that file -- but not errors. That should not have prevented > compilation for that .c file. > > You then went on to run "make check", but that failed predictably because > "make" had already failed. > > You might want to run "make V=1" to see if you can get more details about why > orte/mca/filem/base/filem_base_select.c failed to compile properly. > > It looks like your GitHub clone build failed in exactly the same place. > > There's something about filem_base_select.c that is failing to compile -- > that's what we need more detail on. > > > > > On Sep 18, 2018, at 10:06 AM, Oleg Kmechak wrote: > > > > Hello, > > > > I am student of Physics from University of Warsaw, and new to OpenMPI. > > Currently just trying to compile it from source code(tried both github and > > tar(3.1.2)). > > I am using Windows Linux Subsystem(WLS), Ubuntu. > > > > uname -a: > > >Linux Canopus 4.4.0-17134-Microsoft #285-Microsoft Thu Aug 30 17:31:00 PST > > >2018 x86_64 x86_64 x86_64 GNU/Linux > > > > I have done all steps suggested in INSTALL and HACKING files, installed > > next tool i proper order: M4(1.4.18), autoconf(2.69), automake(1.15.1), > > libtool(2.4.6), flex(2.6.4). > > > > Next I enabled AUTOMAKE_JOBS=4 and ran: > > > > ./autogen.pl #for source code from git hub > > > > Then > > ./configure --disable-picky --enable-mpi-cxx --without-cma --enable-static > > > > I added --without-cma cos I have a lot of warnings about compiling asprintf > > function > > > > and finally: > > make -j 4 all #cos I have 4 logical processors > > > > And in both versions(from github or tar(3.1.2)) it fails. > > Github version error: > > >../../../../opal/mca/hwloc/hwloc201/hwloc/include/hwloc.h:71:10: fatal > > >error: hwloc/bitmap.h: No such file or directory > > #include > > > > And tar(3.1.2) version: > > >libtool: error: cannot find the library '../../ompi/libmpi.la' or > > >unhandled argument '../../ompi/libmpi.la' > > > > Please see also full log in attachment > > Thanks, hope You will help(cos I passed a lot of time on it currently:) ) > > > > > > PS: if this is a bug or unimplemented feature(WLS is probably quite > > specific platform), should I rise issue on github project? > > > > > > Regards, Oleg Kmechak > > > > ___ > > users mailing list > > users@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/users > > > -- > Jeff Squyres > jsquy...@cisco.com > > ___ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users ___ users mailing list
Re: [OMPI users] OpenMPI building fails on Windows Linux Subsystem(WLS).
I can't say that we've tried to build on WSL; the fact that it fails is probably not entirely unsurprising. :-( I looked at your logs, and although I see the compile failure, I don't see any reason *why* it failed. Here's the relevant fail from the tar_openmpi_fail file: - 5523 Making all in mca/filem 5524 make[2]: Entering directory '/mnt/c/Users/ofcra/dev/openmpi-3.1.2/orte/mca/filem' 5525 GENERATE orte_filem.7 5526 CC base/filem_base_frame.lo 5527 CC base/filem_base_select.lo 5528 CC base/filem_base_receive.lo 5529 CC base/filem_base_fns.lo 5530 base/filem_base_receive.c: In function ‘filem_base_process_get_remote_path_cmd’: 5531 base/filem_base_receive.c:250:9: warning: ignoring return value of ‘getcwd’, declared with attribute warn_unused_result [-Wunused-result] 5532 getcwd(cwd, sizeof(cwd)); 5533 ^~~~ 5534 base/filem_base_receive.c:251:9: warning: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result [-Wunused-result] 5535 asprintf(_name, "%s/%s", cwd, filename); 5536 ^~~ 5537 Makefile:1892: recipe for target 'base/filem_base_select.lo' failed 5538 make[2]: *** [base/filem_base_select.lo] Error 1 5539 make[2]: *** Waiting for unfinished jobs 5540 make[2]: Leaving directory '/mnt/c/Users/ofcra/dev/openmpi-3.1.2/orte/mca/filem' 5541 Makefile:2586: recipe for target 'all-recursive' failed 5542 make[1]: *** [all-recursive] Error 1 5543 make[1]: Leaving directory '/mnt/c/Users/ofcra/dev/openmpi-3.1.2/orte' 5544 Makefile:1897: recipe for target 'all-recursive' failed 5545 make: *** [all-recursive] Error 1 - I.e., I see "recipe for target 'base/filem_base_select.lo' failed" -- but there's no error indicating *why* it failed. There were 2 warnings when compiling that file -- but not errors. That should not have prevented compilation for that .c file. You then went on to run "make check", but that failed predictably because "make" had already failed. You might want to run "make V=1" to see if you can get more details about why orte/mca/filem/base/filem_base_select.c failed to compile properly. It looks like your GitHub clone build failed in exactly the same place. There's something about filem_base_select.c that is failing to compile -- that's what we need more detail on. > On Sep 18, 2018, at 10:06 AM, Oleg Kmechak wrote: > > Hello, > > I am student of Physics from University of Warsaw, and new to OpenMPI. > Currently just trying to compile it from source code(tried both github and > tar(3.1.2)). > I am using Windows Linux Subsystem(WLS), Ubuntu. > > uname -a: > >Linux Canopus 4.4.0-17134-Microsoft #285-Microsoft Thu Aug 30 17:31:00 PST > >2018 x86_64 x86_64 x86_64 GNU/Linux > > I have done all steps suggested in INSTALL and HACKING files, installed next > tool i proper order: M4(1.4.18), autoconf(2.69), automake(1.15.1), > libtool(2.4.6), flex(2.6.4). > > Next I enabled AUTOMAKE_JOBS=4 and ran: > > ./autogen.pl #for source code from git hub > > Then > ./configure --disable-picky --enable-mpi-cxx --without-cma --enable-static > > I added --without-cma cos I have a lot of warnings about compiling asprintf > function > > and finally: > make -j 4 all #cos I have 4 logical processors > > And in both versions(from github or tar(3.1.2)) it fails. > Github version error: > >../../../../opal/mca/hwloc/hwloc201/hwloc/include/hwloc.h:71:10: fatal > >error: hwloc/bitmap.h: No such file or directory > #include > > And tar(3.1.2) version: > >libtool: error: cannot find the library '../../ompi/libmpi.la' or > >unhandled argument '../../ompi/libmpi.la' > > Please see also full log in attachment > Thanks, hope You will help(cos I passed a lot of time on it currently:) ) > > > PS: if this is a bug or unimplemented feature(WLS is probably quite specific > platform), should I rise issue on github project? > > > Regards, Oleg Kmechak > > ___ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users -- Jeff Squyres jsquy...@cisco.com ___ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
