[mpich2-dev] build issues with MPE on Windows(32) and MinGW

[jayesh at mcs.anl.gov]

Hi,
 We currently don't provide a mingw compatible library for MPE on windows. Why are you using the MPE header files provided with MPICH2 on windows with mingw?

(PS: The CLOG types are defined using pre-defined windows types. There is no need to include <stdint.h> or <inttypes.h> on windows.)
Regards,
Jayesh
----- Original Message -----
From: "Lisandro Dalcin" <dalcinl at gmail.com>
To: mpich2-dev at mcs.anl.gov
Sent: Monday, November 2, 2009 1:02:46 PM GMT -06:00 US/Canada Central
Subject: [mpich2-dev] build issues with MPE on Windows(32) and MinGW

Anthony, this is unrelated to our previous discussions about -fPIC, so
I'm reporting the issue here. I hope it is the right place. If not,
let me know (perhaps mpich-discuss ??).

This diff at Google Code will be clear enough, I think:

http://code.google.com/p/mpi4py/source/diff?spec=svn522&r=522&format=side&path=/trunk/src/MPE/mpe-log.c

Without these two headers included, my Python ext module fails bad to
build with MinGW. Interestingly, "clog_inttypes.h" has these two
includes commented out on Windows (using the binary installer here).
So perhaps protecting the inclusion of these two headers as shown in
the link above will do the trick? To put it clear, I'm talking about
using this:

   #if defined(_WIN32) && defined(__GNUC__)
     #include <stdint.h>
     #include <inttypes.h>
   #endif


-- 
Lisandro Dalcín
---------------
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594