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 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 
> > 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
<>
___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel

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 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 
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] (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 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)

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 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

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
> 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?
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/12/16444.php
>


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 
> --without-threads --without-hwloc --enable-mca-no-build=maffinity,paffinity 
> --enable-contrib-no-build=libnbc,vt

FWIW, there's no maffinifty/paffinity any more.  And you can just --disable-vt.

> Sadly, the build failed very early:
> 
>   CC runtime/opal_info_support.lo
> runtime/opal_info_support.c: In function 'opal_info_do_params':
> runtime/opal_info_support.c:444:9: error: 'errno' undeclared (first use in 
> this function)
> runtime/opal_info_support.c:444:9: note: each undeclared identifier is 
> reported only once for each function it appears in
> make[2]: *** [runtime/opal_info_support.lo] Error 1
> make[2]: Leaving directory `/a/store-04/h/lab/mosix/alexam02/ompi-jeff/opal'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/a/store-04/h/lab/mosix/alexam02/ompi-jeff/opal'
> make: *** [all-recursive] Error 1
> 
> Should this be a trac ticket?

Seems like it should be an easy fix (e.g., a missing header file?) -- can you 
submit a patch?

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/



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
--enable-contrib-no-build=libnbc,vt

Sadly, the build failed very early:

  CC runtime/opal_info_support.lo
runtime/opal_info_support.c: In function 'opal_info_do_params':
runtime/opal_info_support.c:444:9: error: 'errno' undeclared (first use in
this function)
runtime/opal_info_support.c:444:9: note: each undeclared identifier is
reported only once for each function it appears in
make[2]: *** [runtime/opal_info_support.lo] Error 1
make[2]: Leaving directory `/a/store-04/h/lab/mosix/alexam02/ompi-jeff/opal'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/a/store-04/h/lab/mosix/alexam02/ompi-jeff/opal'
make: *** [all-recursive] Error 1

Should this be a trac ticket?

Alex



On Fri, Sep 6, 2013 at 1:22 PM, Alex Margolin  wrote:

> 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=libnbc,vt && make && make install
>
> When I build and run any MPI app, I'm getting the following error (and the
> app fails):
>
> mpirun: Symbol `orte_process_info' has different size in shared object,
> consider re-linking
> mpirun: Symbol `orte_plm' has different size in shared object, consider
> re-linking
> mpirun: symbol lookup error: mpirun: undefined symbol:
> orte_trigger_event_t_class
>
> Anybody ever stumbled on this or something similar in the past?
>
> Thanks,
> Alex
>
> ___
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>


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
installed and what the user sees:

1) Only install opal{cc,c++} and orte{cc,c++} if configured with --
with-devel-headers.  Right now, they are always installed, but there
are no header files installed for either project, so there's really
not much way for a user to actually compile an OPAL / ORTE  
application.


2) Drop support for opalCC and orteCC.  It's a pain to setup all the
symlinks (indeed, they are currently done wrong for opalCC) and
there's no history like there is for mpiCC.  This isn't a big deal,
but would make two Makefiles easier to deal with.  And since about
every 3 months, I have to fix the Makefiles after they get borked up
a little bit, it makes my life easier.

3) Change what is currently opalcc.1 (name it something generic,
probably opal_wrapper.1) and add some macros that get sed'ed so that
the man pages appear to be customized for the given command.  Josh
and I had talked about this long ago, but time prevented us from
actually doing anything.

4) Install the wrapper data files even if we compiled with --disable-
binaries.  This is for the use case of doing multi-lib builds, where
one word size will only have the library built, but we need both set
of wrapper data files to piece together to activate the multi-lib
support in the wrapper compilers.

Comments?


Brian



--
   Brian Barrett
   Open MPI developer
   http://www.open-mpi.org/


___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel



--
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems