Re: [OMPI devel] Announcing Open MPI v5.0.0rc2

On 10.01.2022 06:50, Marco Atzeri wrote: On 09.01.2022 15:54, Ralph Castain via devel wrote: Hi Marco Try the patch here (for the prrte 3rd-party subdirectory): https://github.com/openpmix/prrte/pull/1173 Ralph Thanks Ralph, I will do on the next build as I need still to test the

Re: [OMPI devel] Announcing Open MPI v5.0.0rc2

On 09.01.2022 15:54, Ralph Castain via devel wrote: Hi Marco Try the patch here (for the prrte 3rd-party subdirectory): https://github.com/openpmix/prrte/pull/1173 Ralph Thanks Ralph, I will do on the next build as I need still to test the current build. To complete the build I also nee

Re: [OMPI devel] Announcing Open MPI v5.0.0rc2

On 01.01.2022 20:07, Barrett, Brian wrote: Marco - There are some patches that haven't made it to the 5.0 branch to make this behavior better. I didn't get a chance to back port them before the holiday break, but they will be in the next RC. That said, the issue below is a warning, not an e

Re: [OMPI devel] Announcing Open MPI v5.0.0rc2

On 18.10.2021 20:39, Austen W Lauria via devel wrote: The second release candidate for the Open MPI v5.0.0 release is posted at: https://www.open-mpi.org/software/ompi/v5.0/ Question: there is a easy way to configure and build the 3rd party inclu

Re: [OMPI devel] Announcing Open MPI v4.0.4rc2

On 06.06.2020 10:37, Ralph Castain via devel wrote: I would have hoped that the added protections we put into PMIx would have resolved ds12 as well as ds21, but it is possible those changes didn't get into OMPI v4.0.x. Regardless, I think you should be just fine using the gds/hash component for

Re: [OMPI devel] Announcing Open MPI v4.0.4rc2

On 05.06.2020 22:29, Marco Atzeri wrote: On 01.06.2020 20:26, Geoffrey Paulsen via devel wrote: Open MPI v4.0.4rc2 is now available for download and test at: sso_last: https://www.open-mpi.org/software/ompi/v4.0/ It builds on Cygwin64 bit, and this time it runs, but the PMIX is throwing

Re: [OMPI devel] Announcing Open MPI v4.0.4rc2

On 01.06.2020 20:26, Geoffrey Paulsen via devel wrote: Open MPI v4.0.4rc2 is now available for download and test at: sso_last: https://www.open-mpi.org/software/ompi/v4.0/ It builds on Cygwin64 bit, and this time it runs, but the PMIX is throwing some errors: $ mpirun -n 4 ./hello_c.exe [LA

Re: [OMPI devel] Please test Open MPI v4.0.4rc1

Am 09.05.2020 um 17:18 schrieb Howard Pritchard via devel: Open MPI v4.0.4rc1 has been posted to https://www.open-mpi.org/software/ompi/v4.0/ 4.0.4 -- May, 2020 --- - Fix an ABI compatibility issue with the Fortran 2008 bindings. Thanks to Alastair McKinstry for reporting

Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

attach_fifo, 0xC000), errno 2 Am 04.02.2020 um 04:17 schrieb Ralph Castain via devel: It is the latter one it is complaining about: /tmp/ompi.LAPTOP-82F08ILC.197609/pid.93/0/debugger_attach_fifo I have no idea why it is complaining. On Feb 3, 2020, at 2:03 PM, Marco Atzeri via devel

Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

Am 03.02.2020 um 18:15 schrieb Ralph Castain via devel: Hi Marco mpirun isn't trying to run a debugger. It is opening a fifo pipe in case a debugger later wishes to attach to the running job - it is used by an MPIR-based debugger to let mpirun know that it is attaching. My guess is that the c

Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

Am 02.02.2020 um 14:16 schrieb Jeff Squyres (jsquyres): On Feb 2, 2020, at 2:17 AM, Marco Atzeri via devel wrote: not a new issue as it was also in 3.1.5. what is causing the last line of warning ? And why a simple run should try to run a debugger ? $ mpirun -n 4 ./hello_c ... Hello, world

Re: [OMPI devel] v3.0.6rc2 and v3.1.6rc2 available for testing

Am 30.01.2020 um 21:39 schrieb Jeff Squyres (jsquyres) via devel: Minor updates since rc1: 3.0.6rc2 and 3.1.6rc2: - Fix run-time linker issues with OMPIO on newer Linux distros. 3.1.6rc2 only: - Fix issue with zero-length blockLength in MPI_TYPE_INDEXED. Please test: https://www.open-mpi.

Re: [OMPI devel] PMIX ERROR: INIT spurious message on 3.1.5

message by simply adding "gds = ^ds21" to your default MCA param file (the pmix one - should be named pmix-mca-params.conf). Artem - any advice here? On Dec 25, 2019, at 9:56 AM, Marco Atzeri via devel wrote: I have no multinode around for testing I will need to setup one for testing

Re: [OMPI devel] PMIX ERROR: INIT spurious message on 3.1.5

is failure, though, since the job seemed to run ok. Are you able to run multi-node jobs ok? On Dec 22, 2019, at 1:20 AM, Marco Atzeri via devel wrote: Hi Developers, Cygwin 64bit, openmpi-3.1.5-1 testing the cygwin package before releasing it I see a never seen before spurious error messages t

[OMPI devel] PMIX ERROR: INIT spurious message on 3.1.5

Hi Developers, Cygwin 64bit, openmpi-3.1.5-1 testing the cygwin package before releasing it I see a never seen before spurious error messages that do not seem about error at all: $ mpirun -n 4 ./hello_c.exe [LAPTOP-82F08ILC:02395] PMIX ERROR: INIT in file /cygdrive/d/cyg_pub/devel/openmpi/v3.1

Re: [OMPI devel] Openmpi configure: Could not determine the fortran compiler flag

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 h

Re: [OMPI devel] openmpi 3.1.x examples

Am 16.07.2018 um 23:05 schrieb Jeff Squyres (jsquyres) via devel: On Jul 13, 2018, at 4:35 PM, Marco Atzeri wrote: For one. The C++ bindings are no longer part of the standard and they are not built by default in v3.1x. They will be removed entirely in Open MPI v5.0.0. Hey Marco -- you

Re: [OMPI devel] Cygwin Fortran compiler options

Am 16.07.2018 um 23:06 schrieb Jeff Squyres (jsquyres) via devel: Split the Fortran issue off into its own thread (and kept it on devel; no need for ompi-packagers) On Jul 13, 2018, at 4:35 PM, Marco Atzeri wrote: the fortran problem is due to a compiler settings It works with $ mpifort

Re: [OMPI devel] openmpi 3.1.x examples

Am 13.07.2018 um 22:07 schrieb Nathan Hjelm via devel: For one. The C++ bindings are no longer part of the standard and they are not built by default in v3.1x. They will be removed entirely in Open MPI v5.0.0. Not sure why the fortran one is not building. the fortran problem is due to a comp

[OMPI devel] openmpi 3.1.x examples

Hi, may be I am missing something obvious, but are the examples still actual C: hello_c.c C++: hello_cxx.cc Fortran mpif.h: hello_mpifh.f Fortran use mpi: hello_usempi.f90 Fortran use mpi_f08: hello_usempif08.f90 Java:Hello.ja

Re: [OMPI devel] openmpi-3.1.0 cygwin patch

On 6/16/2018 6:15 PM, Jeff Squyres (jsquyres) via devel wrote: Thanks Macro. I've filed https://github.com/open-mpi/ompi/pull/5277 here for master; will follow up with PR's to the release branches after that passes CI / is merged. Hi Jeff, please apply both patches the current 3.1.0 packag

Re: [OMPI devel] openmpi-3.1.0 cygwin patch

On 5/28/2018 11:58 AM, Marco Atzeri wrote: On 5/24/2018 11:07 AM, Marco Atzeri wrote: On 5/23/2018 2:58 PM, Gilles Gouaillardet wrote: Marco, Have you tried to build Open MPI with an external (e.g. Cygwin provided) libevent library ? If that works, I think that would be the preferred method

Re: [OMPI devel] openmpi-3.1.0 cygwin patch

On 5/24/2018 11:07 AM, Marco Atzeri wrote: On 5/23/2018 2:58 PM, Gilles Gouaillardet wrote: Marco, Have you tried to build Open MPI with an external (e.g. Cygwin provided) libevent library ? If that works, I think that would be the preferred method. Cheers, Gilles I will try. If I

Re: [OMPI devel] openmpi-3.1.0 cygwin patch

On 5/23/2018 2:58 PM, Gilles Gouaillardet wrote: Marco, Have you tried to build Open MPI with an external (e.g. Cygwin provided) libevent library ? If that works, I think that would be the preferred method. Cheers, Gilles I will try. If I remember right there was an issue in the past as so

[OMPI devel] openmpi-3.1.0 cygwin patch

The attached patch allows the compilation of openmpi-3.1.0 on cygwin 32 and 64 bit with gcc 7.3 It is basically the same already proposed in the past for 2.1.2 I will release the cygwin package as soon we roll out the gcc 7.3 compiler Regards Marco --- origsrc/openmpi-3.1.0/opal/mca/event/libe

Re: [OMPI devel] how to disable memory/patcher build ?

On 31/10/2017 08:50, Gilles Gouaillardet wrote: Marco, can you please give the attached patch a try ? so far, it compiles for me. thanks Gilles, it works btw, i faced some issues (conflicting definitions between windows.h and netdb.h), did you need some patches in order to solve these iss

Re: [OMPI devel] how to disable memory/patcher build ?

ping ? It is a blocking issue for any effort to move on further cygwin release after 1.10.7 https://github.com/open-mpi/ompi/issues/4282 On 28/09/2017 21:33, Marco Atzeri wrote: Hi, restarting the effort to build 2.1.2 on cygwin I hit: make[2]: Entering directory '/cygdrive/e/cyg_pub/

[OMPI devel] how to disable memory/patcher build ?

Hi, restarting the effort to build 2.1.2 on cygwin I hit: make[2]: Entering directory '/cygdrive/e/cyg_pub/devel/openmpi/v2.1/openmpi-2.1.2-1.x86_64/build/opal/mca/memory/patcher' CC memory_patcher_component.lo /cygdrive/e/cyg_pub/devel/openmpi/v2.1/openmpi-2.1.2-1.x86_64/src/openmpi-2.

Re: [OMPI devel] Open MPI 2.1.2rc3 available for testing

On 07/09/2017 16:38, Marco Atzeri wrote: On 07/09/2017 16:29, Jeff Squyres (jsquyres) wrote: On Sep 7, 2017, at 9:09 AM, Marco Atzeri wrote: further issue on cygwin, in addition to an easy libevent issue that I already patched. Is that a patch we should: a) submit upstream to libevent b

Re: [OMPI devel] Open MPI 2.1.2rc3 available for testing

On 07/09/2017 16:29, Jeff Squyres (jsquyres) wrote: On Sep 7, 2017, at 9:09 AM, Marco Atzeri wrote: Yes, "patcher" replaces the old malloc hooks. I don't think we looked at how patcher would function on Cygwin at all -- it probably isn't relevant on Windows, because

Re: [OMPI devel] Open MPI 2.1.2rc3 available for testing

On 07/09/2017 16:29, Jeff Squyres (jsquyres) wrote: On Sep 7, 2017, at 9:09 AM, Marco Atzeri wrote: further issue on cygwin, in addition to an easy libevent issue that I already patched. Is that a patch we should: a) submit upstream to libevent b) patch locally in Open MPI ? Hi Jeff

Re: [OMPI devel] Open MPI 2.1.2rc3 available for testing

30/08/2017 22:48, Howard Pritchard wrote: Hi Folks, Open MPI 2.1.2rc3 tarballs are available for testing at the usual place: https://www.open-mpi.org/software/ompi/v2.1/ further issue on cygwin, in addition to an easy libevent issue that I already patched. it seems "opal/mca/memory/patche

Re: [OMPI devel] Open MPI 2.1.2rc3 available for testing

On 05/09/2017 17:35, Jeff Squyres (jsquyres) wrote: Marco - Remind me: are you running autogen.pl for a Cygwin-specific reason? I'm unable to replicate your issue: - I downloaded the 2.1.2rc3 tarball - I ran autogen.pl in the tarball - I built the tarball (tried both normal build and a VPATH b

Re: [OMPI devel] Open MPI 2.1.2rc3 available for testing

On 30/08/2017 22:48, Howard Pritchard wrote: Hi Folks, Open MPI 2.1.2rc3 tarballs are available for testing at the usual place: https://www.open-mpi.org/software/ompi/v2.1/ Fixes since rc2: Issue #4122: CMA compilation error in SM BTL.    Thanks to Paul Hargrove for catching this. Issue #4

Re: [OMPI devel] query on atomic operations

On 01/04/2016 17:51, Nathan Hjelm wrote: This is done to provide the functionality when the compiler doesn't support inline asm. I do not know how testing is done with the atomics in opal/asm/base atomics so its possible some of them are incorrect. -Nathan I should say that the testing is i

Re: [OMPI devel] PMIX on 2.0.0rc1 and cygwin build

coming week fwiw, with master you will soon be able to do the same thing with pmix (e.g. configure --with-pmix=external ...) I assume no one will really require PMI Exascale on cygwin. So this should solve the issue anyway Regards Marco Cheers, Gilles On 12/24/2015 3:42 AM, Marco Atzeri

[OMPI devel] PMIX on 2.0.0rc1 and cygwin build

building 2.0.0rc1 on cygwin I was stacked on opal/mca/pmix/pmix1xx/pmix Question: - as pmix depends on hwloc and libevents, is it supposed to link against opal shared lib, is it supposed to be included in the opal shared lib or is it a circular dependency ? I solved the build changing from s

Re: [OMPI devel] Open MPI v1.10.2rc1 available

On 19/12/2015 17:35, Ralph Castain wrote: Hello folks Don’t want your holiday to be too boring, so we are also making available the v1.10.2 release candidate for review. We won’t release until sometime in January, but hopefully some of you will have a chance to test it in the meantime. You’ll fi

Re: [OMPI devel] 1.8.5....going once...going twice...

On 4/24/2015 6:52 PM, Ralph Castain wrote: Any last minute issues people need to report? Otherwise, this baby is going to ship Paul: I will include your README suggestions as they relate to 1.8.5. Thanks, as always! Ralph attached patch to avoid the link chains mpif77$(EXEEXT) -> mpifort$(

Re: [OMPI devel] 1.8.5rc2 released

On 4/22/2015 11:19 PM, Jeff Squyres (jsquyres) wrote: Question: what is the scope of the new two shared libs usr/bin/cygmpi_usempi_ignore_tkr-0.dll usr/bin/cygmpi_usempif08-0.dll in comparison to previous usr/bin/cygmpi_mpifh-2.dll usr/bin/cygmpi_usempi-1.dll already present in 1.8.4 ? A

Re: [OMPI devel] 1.8.5rc2 released

On 4/22/2015 12:43 AM, Jeff Squyres (jsquyres) wrote: In the usual location: http://www.open-mpi.org/software/ompi/v1.8/ Making all in mpi/fortran/use-mpi-f08 make[2]: Entering directory '/cygdrive/e/cyg_pub/devel/openmpi/openmpi-1.8.5rc2-1.x86_64/build/ompi/mpi/fortran/use-mpi-f08'

Re: [OMPI devel] 1.8.5rc1 is ready for testing

On 4/20/2015 5:16 PM, Jeff Squyres (jsquyres) wrote: I looked at this thread in a little more detail... The question below is a little moot because of the change that was done to v1.8, but please humor me anyway. :-) Macro: I think you told me before, but I forget, so please refresh my memory

Re: [OMPI devel] 1.8.5rc1 is ready for testing

tomorrow is fine . I am testing octave-4.0.0-rc3 today ;-) On 4/18/2015 9:13 PM, Ralph Castain wrote: I am planning on rc2 on Monday, if you’d prefer to wait On Apr 18, 2015, at 9:30 AM, Marco Atzeri wrote: Are you planning another rc or I should test the git stable repository ?

Re: [OMPI devel] 1.8.5rc1 is ready for testing

Are you planning another rc or I should test the git stable repository ? On 4/18/2015 5:10 PM, Ralph Castain wrote: Should now be solved - it was a libtool compatibility issue, and I updated the 1.8 libtool code On Apr 18, 2015, at 7:57 AM, Marco Atzeri mailto:marco.atz...@gmail.com>>

Re: [OMPI devel] 1.8.5rc1 is ready for testing

On 4/18/2015 1:01 PM, Jeff Squyres (jsquyres) wrote: Marco -- I'm super-late to this -- did this issue get resolved? Not that I am aware of. I was busy on other things and I did not work further on the matter. Suggestion for solving it ? On Apr 7, 2015, at 5:12 PM, Marco Atzeri

Re: [OMPI devel] 1.8.5rc1 is ready for testing

On 4/7/2015 10:00 PM, Ralph Castain wrote: What version of libtool do you have? We require 2.4.2 - newer versions don’t necessarily work, I fear. 2.4.6 for what I can see opal/mca/backtrace/configure.m4 exist on the source tree so it seems a lack of relative/absolute path when invoking mak

Re: [OMPI devel] 1.8.5rc1 is ready for testing

On 4/5/2015 11:42 PM, Ralph Castain wrote: Usual place: http://www.open-mpi.org/software/ompi/v1.8/ building on cygwin64 Making all in libltdl make[2]: Entering directory '/cygdrive/e/cyg_pub/devel/openmpi/openmpi-1.8.5rc1-1.x86_64/build/opal/libltdl' CDPATH="${ZSH_VERSION+.}:" && cd /pub/

Re: [OMPI devel] 1.8.4rc4 now out for testing

On 12/14/2014 12:06 AM, Ralph Castain wrote: Hi folks I’ve rolled up the bug fixes so far, including the thread-multiple performance fix. So please give this one a whirl http://www.open-mpi.org/software/ompi/v1.8/ Ralph No regression on Cygwin 64 bit Only and usual FAIL: atomic_cmpset_noin

[OMPI devel] oshmem only supports Linux ?

Hi, I had the impression that the scope of using autotools is to check for features not platforms. *** OSHMEM Configuration options checking if want oshmem... yes configure: WARNING: OpenSHMEM support was requested, but currently configure: WARNING: only supports Linux. configure: error: Cannot

Re: [OMPI devel] 1.8.2rc2 ready for test

On 24/07/2014 15:52, Ralph Castain wrote: Oshmem should be enabled by default now Ok, so please reverse the configure switch --enable-oshmem Enable building the OpenSHMEM interface (disabled by default) I will test enabling it in the meantime. Regards Marco

Re: [OMPI devel] 1.8.2rc2 ready for test

On 24/07/2014 01:05, Ralph Castain wrote: Usual place: http://www.open-mpi.org/software/ompi/v1.8/ Please test and report problems by Wed July 30 Thanks Ralph on cygwin 64bit, it builds and passes tests except known https://svn.open-mpi.org/trac/ompi/ticket/4195# Question: oshmem was supp

Re: [OMPI devel] Bad parameter in file oob_tcp.c

On 05/03/2014 04:06, Ralph Castain wrote: The code generating the error is here: in->sin_addr.s_addr = inet_addr(host); if (in->sin_addr.s_addr == INADDR_ANY) { return ORTE_ERR_BAD_PARAM; } The address is resolving to INADDR_ANY instead of a regular ad

[OMPI devel] Bad parameter in file oob_tcp.c

noted on cygwin with 1.7.4 and on 1.7.5rc1 $ mpirun -n 4 ./hello_c.exe [MATZERI:06212] [[62628,1],0] ORTE_ERROR_LOG: Bad parameter in file /pub/devel/openmpi/openmpi-1.7.5rc1-1/src/openmpi-1.7.5rc1/orte/mca/oob/tcp/oob_tcp.c at line 292 [MATZERI:05620] [[62628,1],1] ORTE_ERROR_LOG: Bad paramete

Re: [OMPI devel] v1.7.5rc1 posted

On 04/03/2014 20:35, Hjelm, Nathan T wrote: Fixed and CMR'ed to 1.7.5. -Nathan confirmed thanks

Re: [OMPI devel] v1.7.5rc1 posted

On 02/03/2014 03:13, Ralph Castain wrote: In the usual place: http://www.open-mpi.org/software/ompi/v1.7/ Please subject this to your best tests as we hope to roll this (plus bug fixes) to 1.8.0 at the end of the month. This includes the new OSHMEM support, plus a completely updated MPI-3 com

Re: [OMPI devel] 1.7.5 status

On 13/02/2014 16:36, Ralph Castain wrote: Hi Marco Quick question for you: we don't support Windows any more anyway. If we just remove the #if WIN32 cruft, would that solve the problem? in theory yes. Regards Marco

Re: [OMPI devel] 1.7.5 status

On 12/02/2014 04:18, Ralph Castain wrote: Things are looking relatively good - I see two recurring failures: 1. idx_null - no idea what that test does, but it routinely fails 2. intercomm_create - this is the 3-way connect/accept/merge. Nathan - I believe you had a fix for that? Ralph o

Re: [OMPI devel] 1.7.4rc2 is out

On 28/01/2014 04:54, Jeff Squyres (jsquyres) wrote: In the usual location: http://www.open-mpi.org/software/ompi/v1.7/ Lots of changes since 1.7.4rc1, but we didn't keep a good NEWS file between the two, so I can't list them all here. On cygwin 64 bit, except for the known noinline fai

Re: [OMPI devel] trunk build failure on {Free,Net,Open}BSD

Il 1/11/2014 7:54 AM, marco atzeri ha scritto: Il 1/11/2014 4:28 AM, Paul Hargrove ha scritto: Jeff and I iterated a bit off-list and opal/util/path.c in tonight's trunk tarball (1.9a1r30255) works for all of my systems. With the help of Jeff's recently-enhanced test/util/opal_path_n

Re: [OMPI devel] trunk build failure on {Free,Net,Open}BSD

Il 1/11/2014 4:28 AM, Paul Hargrove ha scritto: Jeff and I iterated a bit off-list and opal/util/path.c in tonight's trunk tarball (1.9a1r30255) works for all of my systems. With the help of Jeff's recently-enhanced test/util/opal_path_nfs.c I was able to verify that NFS mounts are now correctly

Re: [OMPI devel] shared lib version on trunk

Il 1/10/2014 3:50 PM, Jeff Squyres (jsquyres) ha scritto: On Jan 10, 2014, at 9:48 AM, marco atzeri <> wrote: building openmpi-1.9a1r30128-1, I notice - # Version information for libmpi. current=0 age=0 revision=0 -- wh

[OMPI devel] shared lib version on trunk

building openmpi-1.9a1r30128-1, I notice - # Version information for libmpi. current=0 age=0 revision=0 -- while on 1.7.3 is -- # Version information for libmpi. current=3 age=2 revision=0 ---

Re: [OMPI devel] trunk build failure on {Free,Net,Open}BSD

Il 1/10/2014 5:00 AM, Paul Hargrove ha scritto: The following might be helpful: http://stackoverflow.com/questions/1653163/difference-between-statvfs-and-statfs-system-calls It seems to indicate that even if one does find a statfs() function, there are multiple os-dependent versions and it shoul

Re: [OMPI devel] 1.7.4rc1 test failure : cygwin 64 bit

Il 1/7/2014 2:54 PM, George Bosilca ha scritto: Can you try with the latest trunk please? Also if things are not going well with the trunk please provide the opal_config.h file. Thanks, George. same failures opal_config.h for openmpi-1.9a1r30128-1 attached. Sorry for delay but buil

Re: [OMPI devel] trunk build failure on {Free,Net,Open}BSD

Il 1/9/2014 5:10 AM, Ralph Castain ha scritto: Actually, as I look at it, the logic escapes me anyway. Basically, you only have two options - use the vfs struct for Sun, and use fs struct for everything else. I'm not aware of any other choice, and indeed the list of all the systems for the latter

[OMPI devel] 1.7.4rc1 test failure : cygwin 64 bit

Failures on cygwin 64bit with gcc-4.8.2. Notes: - cygwin 32bit gives no failure - These failures are not new, they were also present in openmpi-1.7.3-1 and previous - --> Testing atomic_spinlock_noinline.exe /pub/devel/openmpi/ope

Re: [OMPI devel] 1.7.x support statement

'prepare_for_install' => 'MTT::Common::Copytree::PrepareForInstall', 'prepend_path' => undef, 'setenv' => undef, 'refcount' => 0, 'simple_section_name' => 'trivial', 'have_new' => 1,

Re: [OMPI devel] 1.7.x support statement

Il 10/5/2013 1:35 AM, Jeff Squyres (jsquyres) ha scritto: On Oct 4, 2013, at 8:38 AM, marco atzeri wrote: At first glance it does not seems particular user friendly nor with a clear HOWTO guide for good start. How's this for a start: https://svn.open-mpi.org/trac/mtt/wiki/OMPITe

Re: [OMPI devel] 1.7.x support statement

Il 10/4/2013 1:47 PM, Jeff Squyres (jsquyres) ha scritto: Good call; yes. Marco: is there any chance you can run Open MPI through the MPI Testing Tool (MTT) on a regular basis, and submit your results to mtt.open-mpi.org? You can run as few or as many tests a night as you want. For example, t

Re: [OMPI devel] 1.7.x support statement

Il 10/4/2013 1:08 PM, Jeff Squyres (jsquyres) ha scritto: This is in the README -- is it still accurate? I'm thinking that all Solaris support should move to the "lightly but not fully tested" category, for example: - - Systems that have been tested are: - Linux (various flavors/distros

Re: [OMPI devel] Fwd: basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail

Il 7/11/2013 1:47 PM, Vasiliy ha scritto: I've also tracked down that problem with 'test-driver'. Look at that: $ gdb --args /usr/bin/sh /usr/share/automake-1.14/test-driver GNU gdb (GDB) 7.6.50.20130320-cvs Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or l

Re: [OMPI devel] a bogus warning: undefined symbols not allowed in x86_64-pc-cygwin shared libraries

Il 7/9/2013 2:01 PM, Vasiliy ha scritto: Hi, Marco, It is a looong string of characters, times as yours, and I'm actually making a DSO build with everything included. Yes, it is the bleeding-edge, however, patched Open MPI version 1.9a1 sources, on Cygwin 64-bit version 1.7.21-6. I have updated

Re: [OMPI devel] a bogus warning: undefined symbols not allowed in x86_64-pc-cygwin shared libraries

Il 7/8/2013 9:00 PM, Vasiliy ha scritto: I haven't checked that yet, however, from my experience, creating a shared library manually from the same compiled objects never was a problem at a later stage, it's usually because of Makefile's inconsistent dependencies ordering: $ uname -srvmo CYGWIN_N

Re: [OMPI devel] Open MPI 1.7rc9 tarballs up

On 3/28/2013 10:33 PM, Barrett, Brian W wrote: All - What we dearly hope is the final release candidate of 1.7, 1.7rc9,is up at the usual place. I would really like to release this early next week, so if we could all test, that would be great. http://www.open-mpi.org/software/ompi/v1.7/ Th

Re: [OMPI devel] 1.7rc8 is posted

On 2/27/2013 6:52 PM, Jeff Squyres (jsquyres) wrote: The goal is to release 1.7 (final) by the end of this week. New rc posted with fairly small changes: http://www.open-mpi.org/software/ompi/v1.7/ - Fix wrong header file / compilation error in bcol - Support MXM STREAM for isend and ire

Re: [OMPI devel] v1.7.0rc7

On 2/26/2013 3:37 AM, Jeff Squyres (jsquyres) wrote: Marco -- Is it just these 2 patches: r28059 [[BR]] Patch for Cygwin support: use correct DSO/shared library prefix and suffix. Thanks to Marco Atzeri for reporting the issue and providing an initial patch. r28060 [[BR]] Patch for Cygwin

Re: [OMPI devel] v1.7.0rc7

On 2/23/2013 11:45 PM, Ralph Castain wrote: This release candidate is the last one we expect to have before release, so please test it. Can be downloaded from the usual place: http://www.open-mpi.org/software/ompi/v1.7/ Latest changes include: * update of the alps/lustre configure code * fixe

Re: [OMPI devel] RFC: Remove windows support

On 2/18/2013 5:10 PM, Jeff Squyres (jsquyres) wrote: WHAT: Remove all Windows code from the trunk. WHY: This issue keeps coming up over and over and over... [cut] 2. Remove all Windows code. This involves some wholesale removing of components as well as a bunch of #if code throughout the co

[OMPI devel] openmpi-1.9a1r27710 on cygwin: patch and questions

Hi, additional to the patches used for building on cygwin openmpi-1.7rc5, a new one is needed for openmpi-1.9a1r27710 build. See attached for statfs usage. As config parameters, I added "if-windows,shmem-windows" to --enable-mca-no-build=paffinity,installdirs-windows,timer-windows,shmem-sysv,if-

Re: [OMPI devel] openmpi-1.7rc5 on cygwin ; results and patches

On 12/20/2012 1:59 PM, Jeff Squyres wrote: Thank you! I've filed https://svn.open-mpi.org/trac/ompi/ticket/3437 about this. Do you have any Open MPI v1.6-specific patches that would be useful to merge upstream? I've looked through my email and don't see any, but I could be missing them.

[OMPI devel] openmpi-1.7rc5 on cygwin ; results and patches

Built and tested openmpi-1.7rc5 on cygwin, same configuration than 1.6.3-4 package ./autogen.sh configure \ LDFLAGS="-Wl,--export-all-symbols -no-undefined" \ --disable-mca-dso \ --disable-sysv-shmem \ --without-uda