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 <marco.atz...@gmail.com> 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,
ideally (a) as it seems that any new libevent version is causing (b).
I looked at the old patch submitted for 1.7.3 for guidance.
As soon I finish the test I will submit the new patch.
Looking in more depth, we have already libevent as
cygwin package
$ cygcheck -cd |grep event
libevent-devel 2.0.22-1
libevent2.0_5 2.0.22-1
and I see that it builds from source with no patch,
so I see two possibilities:
or there is a version mismatch as from
libevent2022/libevent/configure.ac
it seems a patched 2.0.21-stable and not a 2.0.22
release;
or something is defining WIN32 before configuring
libevent and creating the problem with Cygwin
that requires a lot of
#if defined(WIN32) && !defined(__CYGWIN__)
Regards
Marco
_______________________________________________
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel
