Re: [OMPI devel] (no subject)

2018-10-22 Thread Santiago Serebrinsky
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 yo

Re: [OMPI devel] (no subject)

2018-10-22 Thread Gilles Gouaillardet
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 m

Re: [OMPI devel] (no subject)

2018-10-22 Thread Santiago Serebrinsky
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

Re: [OMPI devel] (no subject)

2018-10-21 Thread Dmitry N. Mikushin
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 l

[OMPI devel] (no subject)

2018-10-21 Thread 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 probl

Re: [OMPI devel] (no subject)

2014-12-09 Thread Kevin Buckley
On 9 December 2014 at 03:29, Howard Pritchard wrote: > Hello Kevin, > > Could you try testing with Open MPI 1.8.3? There was a bug in 1.8.1 > that you are likely hitting in your testing. > > Thanks, > > Howard Bingo! Seems to have got rid of those messages. Thanks.

Re: [OMPI devel] (no subject)

2014-12-08 Thread Howard Pritchard
Hello Kevin, Could you try testing with Open MPI 1.8.3? There was a bug in 1.8.1 that you are likely hitting in your testing. Thanks, Howard 2014-12-07 17:18 GMT-07:00 Kevin Buckley < kevin.buckley.ecs.vuw.ac...@gmail.com>: > Apologies for the lack of a subject line: cut and pasted the body

Re: [OMPI devel] (no subject)

2014-12-07 Thread Kevin Buckley
Apologies for the lack of a subject line: cut and pasted the body before the subject ! Should have been Removing "registering part of your physical memory" warning message Dunno if anyone can fix that in the maling list?

[OMPI devel] (no subject)

2014-12-07 Thread Kevin Buckley
Watcha, have recently come to install the PISM package on top of PETSc, which, in turn is built against OpenMPI 1.8.1 on our Science Faculty HPC Facility, which has SGI C2112 compute nodes with 64GB RAM running on top of CentOS 6. In testing the PETSc deployment out and when running PISM itself,

Re: [OMPI devel] (no subject)

2013-09-06 Thread Jeff Squyres (jsquyres)
On Sep 6, 2013, at 8:06 AM, Alex Margolin wrote: > Sorry for the title and the html... send button got pressed too earl. > > Anyway, I tried to build OMPI without threads at all with the following > command: > > ./configure --prefix=/cs/mosna/alexam02/ompi CFLAGS=-m64 CXXFLAGS=-m64 > --withou

Re: [OMPI devel] (no subject)

2013-09-06 Thread Alex Margolin
Sorry for the title and the html... send button got pressed too earl. Anyway, I tried to build OMPI without threads at all with the following command: ./configure --prefix=/cs/mosna/alexam02/ompi CFLAGS=-m64 CXXFLAGS=-m64 --without-threads --without-hwloc --enable-mca-no-build=maffinity,paffinity

[OMPI devel] (no subject)

2013-09-06 Thread Alex Margolin
Hi, I'm building ompi r29104 with the following command: make distclean && ./autogen.sh && ./configure --prefix=/cs/mosna/alexam02/ompi CFLAGS=-m64 CXXFLAGS=-m64 --without-hwloc --disable-mpi-threads --disable-progress-threads --enable-mca-no-build=maffinity,paffinity --enable-contrib-no-build=li

[OMPI devel] (no subject)

2010-11-30 Thread ananda.mudar
Jeff, George, Ralph Thanks a lot for your clarifications!! - Ananda --- PREVIOUS MESSAGE --- Subject: Re: [OMPI devel] Warning on fork() disappears if I use MPI threads!! From: Jeff Squyres (jsquyres_at_[hidden]) List-Post: devel@lists.open-mpi.org Date: 2010-1

Re: [OMPI devel] (no subject)

2007-04-17 Thread Jeff Squyres
Don't you also need to cast the return of strtol() to an int? On Apr 17, 2007, at 9:12 AM, Sharon Melamed wrote: Hi, I added an MCA parameter and I want the user to apply an Hex value to this parameter (0x…). In order to do so I needed to change the ‘atoi’ call in the mca_base_param.c fi

[OMPI devel] (no subject)

2007-04-17 Thread Sharon Melamed
Hi, I added an MCA parameter and I want the user to apply an Hex value to this parameter (0x...). In order to do so I needed to change the 'atoi' call in the mca_base_param.c file to 'strtol' call. My question is: Can this code run on all platforms? Index: opal/mca/base/mca_base_param.c

Re: [OMPI devel] (no subject)

2006-10-18 Thread Jeff Squyres
These all look good to me. On Oct 18, 2006, at 1:11 AM, Brian Barrett wrote: Hi all - I have four changes I'd like to make to the wrapper compilers (well, more the build system). I figured I'd make them available for public comment before I did any of them, as they would change how things got

[OMPI devel] (no subject)

2006-10-18 Thread Brian Barrett
Hi all - I have four changes I'd like to make to the wrapper compilers (well, more the build system). I figured I'd make them available for public comment before I did any of them, as they would change how things got installed and what the user sees: 1) Only install opal{cc,c++} and orte