Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

From: Ganapathi Kamath (hgkamath_at_[hidden])
Date: 2007-02-27 22:00:05


Justing passing along some information about building on cygwin, if someone
else is trying.
Though I can't comment on whether the modifications are sound or
whether resulting build is workable, it just pushes through the build.

I made the following changes to revision 13777 off
http://svn.open-mpi.org/svn/ompi/trunk

./ompi/mca/common/sm/common_sm_mmap.c
51a52
>#include <sys/uio.h>

./ompi/runtime/ompi_mpi_preconnect.c
26a27
>#include <sys/uio.h>

./opal/include/opal/sys/atomic.h
241c241
< void opal_atomic_init(opal_atomic_lock_t* lock, int value);

---
>void opal_atomic_init(opal_atomic_lock_t* lock, int32_t value);
./opal/mca/paffinity/windows/paffinity_windows.h
33a34
>#include <w32api/windows.h>
./opal/mca/timer/windows/timer_windows_component.c
22c22
< #include "opal/mca/timer/windows/timer_windows_component.h"
---
>#include "opal/mca/timer/windows/timer_windows.h"
I am still trying to figure things out.
[SYRU212-168:02268] *** Process received signal ***
[SYRU212-168:02268] Signal: Segmentation fault (11)
[SYRU212-168:02268] Signal code:  (23)
[SYRU212-168:02268] Failing at address: 0x610c5115
[SYRU212-168:02268] *** End of error message ***
     23 [main] ompi_info 2268 _cygtls::handle_exceptions: Exception: 
STATUS_ACCESS_VIOLATION
   8485 [main] ompi_info 2268 open_stackdumpfile: Dumping stack trace to 
ompi_info.exe.stackdump
Program received signal SIGSEGV, Segmentation fault.
0x61016525 in stack_info::walk () from /usr/bin/cygwin1.dll
(gdb) bt
#0  0x61016525 in stack_info::walk () from /usr/bin/cygwin1.dll
#1  0x7c859dcc in OutputDebugStringA ()
   from /cygdrive/c/WINDOWS/system32/kernel32.dll
#2  0x40010006 in ?? ()
#3  0x00000000 in ?? ()
The build configuration options were
./configure --prefix=/opt/openmpi/openmpi-1.2-svn/bin 
--exec-prefix=/opt/openmpi/openmpi-1.2-svn/bin