The file win_compat.h seems to be very strange (many #defines of function
names, #defines of type names rather than typedefs, etc.). It might make
sense to avoid including it entirely for MinGW (it is included from
opal/include/opal_config_bottom.h), or edit it to be correct for 64-bit
systems. You might want to try commenting out the entire body of
win_compat.h and re-enabling only those parts that are truly necessary
(and don't have MinGW headers that should be used instead, such as for
ssize_t).
-- Jeremiah Willcock
On Tue, 20 Aug 2013, Richard Haney wrote:
Ah! Thanks, Jeff. Here is a link to the relevant zip file
"openmpi-1.6.5_configure_and_make.zip". It contains the
modified configure (essentially replacing the compound "if" statement that
assigns ompi_cv_asm_arch="IA32"
because my "long" is size 4); the replacement is the simply the alternative
assignment that configure would chose if
my "long" size were not 4:
ompi_cv_asm_arch="AMD64"
The zip file contains:
configure_modified
config.log openmpi-1.6.5_configure.out (the output of configure executed
from within another script)
make_-j_2.out (the output from the parallel attempt at make), and
make.out--(nonparallel make).out
The make command still does not get past the building of of asm.c in
/openmpi-1.6.5/opal/asm
I ran the nonparallel make to eliminate any confusion over the parallel
creation of object file atomic-asm.o in
subdirectory .libs by command
CPPAS atomic-asm.lo
at the same time that the command
CC asm.lo
was about to "crash" with lots of warnings and with seemingly uninformative
"Error" messages.
On Tue, Aug 20, 2013 at 2:20 PM, Jeff Squyres (jsquyres)
<jsquy...@cisco.com> wrote:
Google drive?
