[OMPI devel] Openmpi configure: Could not determine the fortran compiler flag
Hi all, I am using Msys2 from PortableApps under Win10. More precisely, $ uname -a MSYS_NT-10.0-WOW Galapagos 2.11.1(0.329/5/3) 2018-09-10 13:25 i686 Msys I mean to install openmpi. Since I found no pre-built package (I would love to have it!), I downloaded openmpi-3.1.2. When I ./configure --prefix=$HOME/usr/local after many config detections, I get checking for Fortran compiler module include flag... configure: WARNING: *** Could not determine the fortran compiler flag to indicate where modules reside configure: error: *** Cannot continue ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
[OMPI devel] (no subject)
Hi all, I am using Msys2 from PortableApps under Win10. More precisely, $ uname -a MSYS_NT-10.0-WOW Galapagos 2.11.1(0.329/5/3) 2018-09-10 13:25 i686 Msys I mean to install openmpi. Since I found no pre-built package (I would love to have it!), I downloaded openmpi-3.1.2. After having problems with Fortran (posted in another thread), I tried ./configure --prefix=$HOME/usr/local --disable-mpi-fortran In this case configure went somewhat further than before, but I got later the error configure: WARNINGS: neither statfs() and statvfs() were found error: Cannot continue ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
[OMPI devel] Build under Msys2. configure: WARNINGS: neither statfs() and statvfs() were found - error: Cannot continue
Hi all, I am using Msys2 from PortableApps under Win10. More precisely, $ uname -a MSYS_NT-10.0-WOW Galapagos 2.11.1(0.329/5/3) 2018-09-10 13:25 i686 Msys I mean to install openmpi. Since I found no pre-built package (I would love to have it!), I downloaded openmpi-3.1.2. After having problems with Fortran (posted in another thread), I tried ./configure --prefix=$HOME/usr/local --disable-mpi-fortran In this case configure went somewhat further than before, but I got later the error configure: WARNINGS: neither statfs() and statvfs() were found error: Cannot continue I am attaching config.log (renamed to keep track of the error produced). This post replaces a previous one with no subject and no attachment. <> ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Openmpi configure: Could not determine the fortran compiler flag
Compiler: $ which gfortran.exe /mingw64/bin/gfortran.exe I am attaching config.log (renamed to keep track of the error produced). PS: To try moving further, I did ./configure --prefix=$HOME/usr/local --disable-mpi-fortran which led me to a later error. This is posted in a separate thread. On Sun, Oct 21, 2018 at 2:25 PM Jeff Squyres (jsquyres) via devel < devel@lists.open-mpi.org> wrote: > Also, please send the entire output from configure as well as the > config.log file (please compress). > > Thanks! > > > > On Oct 21, 2018, at 4:08 AM, Marco Atzeri > wrote: > > > > Am 21.10.2018 um 09:56 schrieb Santiago Serebrinsky: > >> Hi all, > >> I am using Msys2 from PortableApps under Win10. More precisely, > >> |$ uname -a MSYS_NT-10.0-WOW Galapagos 2.11.1(0.329/5/3) 2018-09-10 > 13:25 i686 Msys | > >> I mean to install openmpi. Since I found no pre-built package (I would > love to have it!), I downloaded openmpi-3.1.2. When I > >> |./configure --prefix=$HOME/usr/local | > >> after many config detections, I get > >> |checking for Fortran compiler module include flag... configure: > WARNING: *** Could not determine the fortran compiler flag to indicate > where modules reside configure: error: *** Cannot continue| > > > > what fortran compiler do you have ? > > > > --- > > Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. > > https://www.avast.com/antivirus > > > > ___ > > devel mailing list > > devel@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/devel > > > -- > Jeff Squyres > jsquy...@cisco.com > > ___ > 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
Re: [OMPI devel] (no subject)
Thanks Dmitry. I was aware of the two links posted... [1]: It dates from 2016, and the issue with statfs/stavfs persists. I wouldn't know how to "submit a pull request with a PKGBUILD for the package", and from the post I did not understand if that is like a "feature request", or if that provides a version that lets me move forward immediately. In the latter case I would certainly do it. [2]: To get a "real" linux (Ubuntu) under Win10 I could get WSL (as you indicate) or another Virtual Machine (e.g., vbox). Both require admin rights, so it would be a longer process (if possible at all) in my corporate environment. On Sun, Oct 21, 2018 at 9:31 PM Dmitry N. Mikushin wrote: > MSYS2 is known for not supplying statfs/statvfs, which are practically > meaningless in a Windows-based environment, see e.g. [1] > > Yet, both calls do not seem to be critical for MPI internals, thus one can > potentially develop patches to turn them into an optional feature within > OpenMPI. > > If you are looking for quick OpenMPI solution on Windows, you may want to > look into Ubuntu terminal for Windows, where OpenMPI works perfectly. > > [1] > https://sourceforge.net/p/msys2/mailman/msys2-users/thread/CAPsJ1NYOZsA7Ge8kj4G%2BNy1X6x7mYyhErDHfKqWfcCQh6DAB%3Dw%40mail.gmail.com/ > [2] https://tutorials.ubuntu.com/tutorial/tutorial-ubuntu-on-windows#0 > > > пн, 22 окт. 2018 г. в 0:52, Santiago Serebrinsky : > >> Hi all, >> >> I am using Msys2 from PortableApps under Win10. More precisely, >> >> $ uname -a >> MSYS_NT-10.0-WOW Galapagos 2.11.1(0.329/5/3) 2018-09-10 13:25 i686 Msys >> >> I mean to install openmpi. Since I found no pre-built package (I would >> love to have it!), I downloaded openmpi-3.1.2. >> >> After having problems with Fortran (posted in another thread), I tried >> >> ./configure --prefix=$HOME/usr/local --disable-mpi-fortran >> >> In this case configure went somewhat further than before, but I got later >> the error >> >> configure: WARNINGS: neither statfs() and statvfs() were found >> error: Cannot continue >> >> ___ >> 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 ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] (no subject)
Dear Gilles, I did what you suggested $ pacman -Syu (a few times, until no further updates) $ pacman -S msys2-runtime-devel but I still get the same error. I am attaching the corresponding log file. I note that Dmitry mentioned that statf/statvfs are not provided in Msys2, so I wonder how you got it with msys2-runtime-devel (which I added). On Mon, Oct 22, 2018 at 5:26 AM Gilles Gouaillardet wrote: > Santiago, > > > the config.log reports there is no /usr/include/sys/statfs.h on your > system. > > on my system, this file exists and is provided by the > msys2-runtime-devel file, > > so the first steps are to check this package is installed and if not, > install it. > > > note I ran pacman -Syu a few times to make sure my system is up to date. > > > Cheers, > > > Gilles > > > On 10/22/2018 5:13 PM, Santiago Serebrinsky wrote: > > Thanks Dmitry. > > > > I was aware of the two links posted... > > > > [1]: It dates from 2016, and the issue with statfs/stavfs persists. > > I wouldn't know how to "submit a pull request with a PKGBUILD for the > > package", and from the post I did not understand if that is like a > > "feature request", or if that provides a version that lets me move > > forward immediately. In the latter case I would certainly do it. > > > > [2]: To get a "real" linux (Ubuntu) under Win10 I could get WSL (as > > you indicate) or another Virtual Machine (e.g., vbox). Both require > > admin rights, so it would be a longer process (if possible at all) in > > my corporate environment. > > > > > > On Sun, Oct 21, 2018 at 9:31 PM Dmitry N. Mikushin > > mailto:maemar...@gmail.com>> wrote: > > > > MSYS2 is known for not supplying statfs/statvfs, which are > > practically meaningless in a Windows-based environment, see e.g. [1] > > > > Yet, both calls do not seem to be critical for MPI internals, thus > > one can potentially develop patches to turn them into an optional > > feature within OpenMPI. > > > > If you are looking for quick OpenMPI solution on Windows, you may > > want to look into Ubuntu terminal for Windows, where OpenMPI works > > perfectly. > > > > [1] > > > https://sourceforge.net/p/msys2/mailman/msys2-users/thread/CAPsJ1NYOZsA7Ge8kj4G%2BNy1X6x7mYyhErDHfKqWfcCQh6DAB%3Dw%40mail.gmail.com/ > > [2] > https://tutorials.ubuntu.com/tutorial/tutorial-ubuntu-on-windows#0 > > > > > > пн, 22 окт. 2018 г. в 0:52, Santiago Serebrinsky > > mailto:sserebrin...@gmail.com>>: > > > > Hi all, > > > > I am using Msys2 from PortableApps under Win10. More precisely, > > > > |$ uname -a MSYS_NT-10.0-WOW Galapagos 2.11.1(0.329/5/3) > > 2018-09-10 13:25 i686 Msys | > > > > I mean to install openmpi. Since I found no pre-built package > > (I would love to have it!), I downloaded openmpi-3.1.2. > > > > After having problems with Fortran (posted in another thread), > > I tried > > > > |./configure --prefix=$HOME/usr/local --disable-mpi-fortran | > > > > In this case configure went somewhat further than before, but > > I got later the error > > > >configure: WARNINGS: neither statfs() and statvfs() were found > >error: Cannot continue > > > > ___ > > devel mailing list > > devel@lists.open-mpi.org <mailto:devel@lists.open-mpi.org> > > https://lists.open-mpi.org/mailman/listinfo/devel > > > > ___ > > devel mailing list > > devel@lists.open-mpi.org <mailto: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 > > ___ > 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
Re: [OMPI devel] Openmpi configure: Could not determine the fortran compiler flag
Precisely, that was the problem. I disabled Fortran support to move ahead and see if I could manage that way (and I found I couldn't!), at least in some of my uses. But I (and perhaps others as well) would still need to have Fortran support, so the issue is not moot at all. Thanks On Mon, Oct 22, 2018 at 1:52 PM Jeff Squyres (jsquyres) wrote: > For what it's worth, it looks like Open MPI's configure found your mingw > fortran compiler, but was unable to determine what flag to use to find > fortran modules -- that's what caused configure to abort. > > From your later messages, it looks like you just ended up disabling > Fortran support, so this is somewhat moot, but I wanted to tie up this > email thread for the archive. > > > > On Oct 21, 2018, at 6:01 PM, Santiago Serebrinsky < > sserebrin...@gmail.com> wrote: > > > > Compiler: > > $ which gfortran.exe > > /mingw64/bin/gfortran.exe > > > > I am attaching config.log (renamed to keep track of the error produced). > > > > PS: To try moving further, I did > > ./configure --prefix=$HOME/usr/local --disable-mpi-fortran > > which led me to a later error. This is posted in a separate thread. > > > > > > On Sun, Oct 21, 2018 at 2:25 PM Jeff Squyres (jsquyres) via devel < > devel@lists.open-mpi.org> wrote: > > Also, please send the entire output from configure as well as the > config.log file (please compress). > > > > Thanks! > > > > > > > On Oct 21, 2018, at 4:08 AM, Marco Atzeri > wrote: > > > > > > Am 21.10.2018 um 09:56 schrieb Santiago Serebrinsky: > > >> Hi all, > > >> I am using Msys2 from PortableApps under Win10. More precisely, > > >> |$ uname -a MSYS_NT-10.0-WOW Galapagos 2.11.1(0.329/5/3) 2018-09-10 > 13:25 i686 Msys | > > >> I mean to install openmpi. Since I found no pre-built package (I > would love to have it!), I downloaded openmpi-3.1.2. When I > > >> |./configure --prefix=$HOME/usr/local | > > >> after many config detections, I get > > >> |checking for Fortran compiler module include flag... configure: > WARNING: *** Could not determine the fortran compiler flag to indicate > where modules reside configure: error: *** Cannot continue| > > > > > > what fortran compiler do you have ? > > > > > > --- > > > Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. > > > https://www.avast.com/antivirus > > > > > > ___ > > > devel mailing list > > > devel@lists.open-mpi.org > > > https://lists.open-mpi.org/mailman/listinfo/devel > > > > > > -- > > Jeff Squyres > > jsquy...@cisco.com > > > > ___ > > devel mailing list > > devel@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/devel > > > > > -- > Jeff Squyres > jsquy...@cisco.com > > ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Open MPI vs msys2
Gilles, You are right, I have $ pacman -Ql msys2-runtime-devel | grep stat msys2-runtime-devel /usr/include/cygwin/stat.h msys2-runtime-devel /usr/include/sys/stat.h msys2-runtime-devel /usr/include/sys/statfs.h msys2-runtime-devel /usr/include/sys/statvfs.h So I wouldn't know why the error message. The following lines from config.log (previously attached) seem puzzling to me: configure:65237: checking for sys/stat.h configure:65237: result: yes configure:65237: checking sys/statfs.h usability configure:65237: gcc -c -O3 -DNDEBUG -finline-functions -fno-strict-aliasing conftest.c >&5 conftest.c:423:10: fatal error: sys/statfs.h: No such file or directory #include ^~ compilation terminated. On one hand, it seems that /usr/include is in the search path for headers (stat.h is found). On the other hand, statfs.h is not found, as if /usr/include were not in the search path for headers. If I try export CPATH=/usr/include export C_INCLUDE_PATH=/usr/include export CPLUS_INCLUDE_PATH=/usr/include I get other, much earlier errors. On Mon, Oct 22, 2018 at 9:20 PM Gilles Gouaillardet wrote: > Santiago, > > > I downloaded and installed msys2 from https://www.msys2.org, and here is > what I have on my system > > > gilles@gilles-PC MINGW32 ~ > $ uname -a > MINGW32_NT-6.1-WOW gilles-PC 2.11.1(0.329/5/3) 2018-09-10 13:25 i686 Msys > > gilles@gilles-PC MINGW32 ~ > $ pacman -Qi msys2-runtime-devel > Name: msys2-runtime-devel > Version : 2.11.1-2 > Description : MSYS2 headers and libraries > Architecture: i686 > URL : https://www.cygwin.com/ > Licenses: GPL > Groups : msys2-devel > Provides: None > Depends On : msys2-runtime=2.11.1 > Optional Deps : None > Required By : None > Optional For: None > Conflicts With : libcatgets-devel > Replaces: libcatgets-devel > Installed Size : 27.12 MiB > Packager: Alexey Pavlov > Build Date : Mon, Sep 10, 2018 7:15:17 PM > Install Date: Tue, Oct 23, 2018 9:06:42 AM > Install Reason : Explicitly installed > Install Script : No > Validated By: Signature > > > gilles@gilles-PC MINGW32 ~ > $ pacman -Ql msys2-runtime-devel | grep stat > msys2-runtime-devel /usr/include/cygwin/stat.h > msys2-runtime-devel /usr/include/sys/stat.h > msys2-runtime-devel /usr/include/sys/statfs.h > msys2-runtime-devel /usr/include/sys/statvfs.h > > > These observations directly conflict with Dimitry's statement (and the > link does not state statfs.h and friends > > are not available on msys2) > > > Cheers, > > > Gilles > > > On 10/23/2018 1:44 AM, Santiago Serebrinsky wrote: > > Dear Gilles, > > > > I did what you suggested > > $ pacman -Syu (a few times, until no further updates) > > $ pacman -S msys2-runtime-devel > > > > but I still get the same error. I am attaching the corresponding log > file. > > I note that Dmitry mentioned that statf/statvfs are not provided in > > Msys2, so I wonder how you got it with msys2-runtime-devel (which I > > added). > > > > > > > > On Mon, Oct 22, 2018 at 5:26 AM Gilles Gouaillardet > <mailto:gil...@rist.or.jp>> wrote: > > > > Santiago, > > > > > > the config.log reports there is no /usr/include/sys/statfs.h on > > your system. > > > > on my system, this file exists and is provided by the > > msys2-runtime-devel file, > > > > so the first steps are to check this package is installed and if not, > > install it. > > > > > > note I ran pacman -Syu a few times to make sure my system is up to > > date. > > > > > > Cheers, > > > > > > Gilles > > > > > > On 10/22/2018 5:13 PM, Santiago Serebrinsky wrote: > > > Thanks Dmitry. > > > > > > I was aware of the two links posted... > > > > > > [1]: It dates from 2016, and the issue with statfs/stavfs persists. > > > I wouldn't know how to "submit a pull request with a PKGBUILD > > for the > > > package", and from the post I did not understand if that is like a > > > "feature request", or if that provides a version that lets me move > > > forward immediately. In the latter case I would certainly do it. > > > > > > [2]: To get a "real" linux (Ubuntu) under Win10 I could get WSL (as > > > you indicate) or another Virtual Machine (e.g., vbox). Both require > > > admin rights, so it would be a longer proc
Re: [OMPI devel] Open MPI vs msys2
This seems quite undesirable. Do you have any idea if this is going to be fixed? I look forward to your update. Cheers, Santiago On Tue, Oct 23, 2018 at 9:57 AM Gilles Gouaillardet < gilles.gouaillar...@gmail.com> wrote: > Meanwhile I found gcc from the gcc package looks for headers in > /usr/include, but gcc from mingw does not (!) > > I found a few misc issues, and I will update hopefully soon. > > Cheers, > > Gilles > > Santiago Serebrinsky wrote: > Gilles, > > You are right, I have > > $ pacman -Ql msys2-runtime-devel | grep stat > msys2-runtime-devel /usr/include/cygwin/stat.h > msys2-runtime-devel /usr/include/sys/stat.h > msys2-runtime-devel /usr/include/sys/statfs.h > msys2-runtime-devel /usr/include/sys/statvfs.h > > So I wouldn't know why the error message. > The following lines from config.log (previously attached) seem puzzling to > me: > > configure:65237: checking for sys/stat.h > configure:65237: result: yes > configure:65237: checking sys/statfs.h usability > configure:65237: gcc -c -O3 -DNDEBUG -finline-functions > -fno-strict-aliasing conftest.c >&5 > conftest.c:423:10: fatal error: sys/statfs.h: No such file or directory > #include > ^~ > compilation terminated. > > On one hand, it seems that /usr/include is in the search path for headers > (stat.h is found). > On the other hand, statfs.h is not found, as if /usr/include were not in > the search path for headers. > > If I try > > export CPATH=/usr/include > export C_INCLUDE_PATH=/usr/include > export CPLUS_INCLUDE_PATH=/usr/include > > I get other, much earlier errors. > > > > > > On Mon, Oct 22, 2018 at 9:20 PM Gilles Gouaillardet > wrote: > >> Santiago, >> >> >> I downloaded and installed msys2 from https://www.msys2.org, and here is >> what I have on my system >> >> >> gilles@gilles-PC MINGW32 ~ >> $ uname -a >> MINGW32_NT-6.1-WOW gilles-PC 2.11.1(0.329/5/3) 2018-09-10 13:25 i686 Msys >> >> gilles@gilles-PC MINGW32 ~ >> $ pacman -Qi msys2-runtime-devel >> Name: msys2-runtime-devel >> Version : 2.11.1-2 >> Description : MSYS2 headers and libraries >> Architecture: i686 >> URL : https://www.cygwin.com/ >> Licenses: GPL >> Groups : msys2-devel >> Provides: None >> Depends On : msys2-runtime=2.11.1 >> Optional Deps : None >> Required By : None >> Optional For: None >> Conflicts With : libcatgets-devel >> Replaces: libcatgets-devel >> Installed Size : 27.12 MiB >> Packager: Alexey Pavlov >> Build Date : Mon, Sep 10, 2018 7:15:17 PM >> Install Date: Tue, Oct 23, 2018 9:06:42 AM >> Install Reason : Explicitly installed >> Install Script : No >> Validated By: Signature >> >> >> gilles@gilles-PC MINGW32 ~ >> $ pacman -Ql msys2-runtime-devel | grep stat >> msys2-runtime-devel /usr/include/cygwin/stat.h >> msys2-runtime-devel /usr/include/sys/stat.h >> msys2-runtime-devel /usr/include/sys/statfs.h >> msys2-runtime-devel /usr/include/sys/statvfs.h >> >> >> These observations directly conflict with Dimitry's statement (and the >> link does not state statfs.h and friends >> >> are not available on msys2) >> >> >> Cheers, >> >> >> Gilles >> >> >> On 10/23/2018 1:44 AM, Santiago Serebrinsky wrote: >> > Dear Gilles, >> > >> > I did what you suggested >> > $ pacman -Syu (a few times, until no further updates) >> > $ pacman -S msys2-runtime-devel >> > >> > but I still get the same error. I am attaching the corresponding log >> file. >> > I note that Dmitry mentioned that statf/statvfs are not provided in >> > Msys2, so I wonder how you got it with msys2-runtime-devel (which I >> > added). >> > >> > >> > >> > On Mon, Oct 22, 2018 at 5:26 AM Gilles Gouaillardet > > <mailto:gil...@rist.or.jp>> wrote: >> > >> > Santiago, >> > >> > >> > the config.log reports there is no /usr/include/sys/statfs.h on >> > your system. >> > >> > on my system, this file exists and is provided by the >> > msys2-runtime-devel file, >> > >> > so the first steps are to check this package is installed and if >> not, >> > install it. >> > >> > >> > note I ran pacman -Syu a few times to make sure my syst
