<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE>.hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
<META content="MSHTML 6.00.6000.16825" name=GENERATOR></HEAD>
<BODY class=hmmessage>
<DIV dir=ltr align=left><SPAN class=599074716-04052009><FONT face=Arial
color=#0000ff>Hi,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=599074716-04052009><FONT face=Arial
color=#0000ff> You can track the progress on this feature at <A
href="https://trac.mcs.anl.gov/projects/mpich2/ticket/568">https://trac.mcs.anl.gov/projects/mpich2/ticket/568</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=599074716-04052009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=599074716-04052009><FONT face=Arial
color=#0000ff>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=599074716-04052009><FONT face=Arial
color=#0000ff>Jayesh</FONT></SPAN></DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT face=Tahoma><B>From:</B>
mpich-discuss-bounces@mcs.anl.gov [mailto:mpich-discuss-bounces@mcs.anl.gov]
<B>On Behalf Of </B>Jayesh Krishna<BR><B>Sent:</B> Monday, May 04, 2009 9:37
AM<BR><B>To:</B> 'ting lei'<BR><B>Cc:</B>
mpich-discuss@mcs.anl.gov<BR><B>Subject:</B> Re: [mpich-discuss] question
regarding compiling/linking underMingW (MPICH2 1.08)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=447371214-04052009><FONT face=Arial
color=#0000ff>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=447371214-04052009></SPAN><FONT face=Arial><FONT
color=#0000ff> <SPAN class=447371214-04052009>We need to update the code
required to generate the gcc libs for a 64-bit version of the libs. Are you
planning to create 64-bit binaries using gcc ?</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN class=447371214-04052009> I
will take a look at the effort required for the change and let you know if we
can push it into the upcoming release candidate.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=447371214-04052009></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff>R<SPAN
class=447371214-04052009>egards,</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=447371214-04052009>Jayesh</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=447371214-04052009></SPAN></FONT></FONT> </DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma><B>From:</B> ting lei [mailto:leitingl@hotmail.com]
<BR><B>Sent:</B> Sunday, May 03, 2009 4:45 PM<BR><B>To:</B>
jayesh@mcs.anl.gov<BR><B>Cc:</B> mpich-discuss@mcs.anl.gov<BR><B>Subject:</B>
RE: [mpich-discuss] question regarding compiling/linking under MingW (MPICH2
1.08)<BR></FONT><BR></DIV>
<DIV></DIV>Hi, Jayesh,<BR><BR>I was trying the new 1.08p1 version of MPICH2 on
Windows Vista64. I heard from you that we need <FONT face=Arial
color=#0000ff>the gcc libs, *.a, with 64-bit version</FONT><BR>Could you
please send a copy of that to me or somehow make it available
online?<BR><BR>Many thanks for your help!<BR><BR>Ting<BR><BR>
<HR id=stopSpelling>
From: leitingl@hotmail.com<BR>To: jayesh@mcs.anl.gov<BR>Date: Tue, 6 Jan 2009
11:45:21 +0000<BR>CC: mpich-discuss@mcs.anl.gov<BR>Subject: Re: [mpich-discuss]
question regarding compiling/linking under MingW (MPICH2 1.08)<BR><BR>
<STYLE>.ExternalClass .EC_hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
.ExternalClass BODY.EC_hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
Hi, Jayesh,<BR> <BR>Thanks a lot for your reply. Solution 1) works
well on the Win64 machine.<BR>"<BR><FONT face=Arial color=#0000ff>However
we don't ship the gcc libs, *.a, with 64-bit version of MPICH2. Let me know
if you need them.). </FONT><BR>"<BR>also, could you please make the gcc libs *.a
available somehow?<BR> <BR>I didn't try cygwin because I heard about
comflicts with mingw dll's, and also about the performance cost of using cygwin
vs. mingw. But it's only rumors, I don't really know if there is any big
performance impact. Currently, I am happy with MPICH2+mingw
working.<BR> <BR>Many thanks for your help<BR> <BR>T.<BR><BR>
<HR id=EC_stopSpelling>
<BR>From: jayesh@mcs.anl.gov<BR>To: leitingl@hotmail.com<BR>CC:
mpich-discuss@mcs.anl.gov<BR>Subject: RE: [mpich-discuss] question regarding
compiling/linking under MingW (MPICH2 1.08)<BR>Date: Mon, 5 Jan 2009 16:55:15
-0600<BR><BR><BR>
<STYLE>.ExternalClass .EC_hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
.ExternalClass BODY.EC_hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009>Hi,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009> Glad to know MPICH2+MingW is working for
you in 32-bit windows.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009> There are two ways to fix your problem with
MPICH2+MingW on 64-bit windows,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009>1) Use 32-bit version of MPICH2 on your 64-bit
windows machine (Uninstall any 64-bit version of MPICH2 before you install
32-bit version of MPICH2). AFAIK Cygwin distributions are 32-bit and we provide
default support for Cygwin+gcc on 32-bit platforms only.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009>2) Let us know if you want to build 64-bit
binaries using MPICH2+MingW (The defns for windows fixed width ints - __int* -
is in _mingw.h, which is included by all MingW header files. So include
<sys/types.h> before including "mpi.h" and you should be able to get rid
of errors with undefined MS-extended types. However we don't ship the gcc libs,
*.a, with 64-bit version of MPICH2. Let me know if you need them.).
</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009> If you want to compile MPICH2
on windows (without using Visual Studio compiler) try compiling MPICH2
using Cygwin. Let us know if it works for you (We regularly test MPICH2+Cygwin.
You won't have the problem with unsupported poll() if you use Cygwin - Cygwin
libs do the abstraction for you.).</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009> Let us know the
results.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009>Regards,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_049304215-05012009>Jayesh</SPAN></FONT></DIV><BR>
<DIV class=EC_EC_OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma><B>From:</B> mpich-discuss-bounces@mcs.anl.gov
[mailto:mpich-discuss-bounces@mcs.anl.gov] <B>On Behalf Of </B>ting
lei<BR><B>Sent:</B> Sunday, January 04, 2009 5:46 PM<BR><B>To:</B>
mpich-discuss@mcs.anl.gov<BR><B>Subject:</B> Re: [mpich-discuss] question
regarding compiling/linking under MingW (MPICH2 1.08)<BR></FONT><BR></DIV>
<DIV></DIV>Hi,<BR> <BR>Thanks a lot for your reply. <BR>I just read an
infinitely long post that discusses whether __int64 is dead, and realized that I
get into something taboo regarding ms specific vs c99. <BR>There is a
lot of discussion of aethetics there, ..., to no avail though.<BR> <BR>Just
for the sake of the problem, I used the binary distribution for Win64. Below is
my MPICH2/lib <BR>$ ls /c/MPICH2/lib/<BR>TraceInput.lib
fmpe.lib irlog2rlog.lib
mpi.lib<BR>cxx.lib
fmpich2.lib mpe.lib
rlog.lib<BR> <BR>In the win32 version, I did see libmpi.a in the same
folder. But I tried removing that file, and was able to compile and
link.<BR> <BR>My last effort was to use <BR>typedef long long
MPI_Aint<BR>and go back to mingw+gcc3.4.5+vista64, and the error message
was:<BR> <BR>$ gcc -I /c/MPICH2/include/ test.c -L /c/MPICH2/lib/
-lmpi <BR>C:/Users/ting/AppData/Local/Temp/cciBiEaP.o:test.c:(.text+0x38):
undefined reference to
`MPI_Init'<BR>C:/Users/ting/AppData/Local/Temp/cciBiEaP.o:test.c:(.text+0x4b):
undefined reference to `MPI_Comm_rank'<BR>collect2: ld returned 1 exit
status<BR> <BR>As a side note, I tried to compile one from source using
mingw under Win64, <BR>but it was complaining about missing poll() function etc.
Somebody complained in a MingW list, but a mingw person believes that MPI under
windows shouldn't<BR>use poll() anyways. I tried to add some other code
downloaded from the internet that fakes a poll(), then I got a problem with
threads. And I realized that the job is<BR>beyond a novice like
me.<BR> <BR>Thanks again for your help,<BR>hope some day this problem will
disappear. But maybe the mingw idea was wrong -- a minimal set of unix functions
with native winxx impl. Lovely little piece that brings <BR>unix to the dull
windows command line though.<BR> <BR> <BR>T.<BR><BR><BR><BR>> Date:
Sun, 4 Jan 2009 20:21:42 +0100<BR>> From: ddkrause@uni-bonn.de<BR>> To:
mpich-discuss@mcs.anl.gov<BR>> Subject: Re: [mpich-discuss] question
regarding compiling/linking under MingW (MPICH2 1.08)<BR>> <BR>>
Hi,<BR>> <BR>> ting lei wrote:<BR>> > *Hi, Dorian*<BR>>
><BR>> > Thanks a lot for your prompt reply.<BR>> > Your command
line<BR>> > > gcc -I /c/MPICH2/include/ test.c -L/c/MPICH2/lib/
-lmpi<BR>> > solves the first problem perfectly on win32.<BR>> <BR>>
Good to hear.<BR>> <BR>> ><BR>> > On Win64, I see the following
from line 333 onwards about MPI_Aint<BR>> > "<BR>> > /* Definitions
that are determined by configure. */<BR>> > typedef __int64
MPI_Aint;<BR>> > typedef int MPI_Fint;<BR>> > #define
MPI_AINT_FMT_DEC_SPEC "%I64d"<BR>> > #define MPI_AINT_FMT_HEX_SPEC
"%I64x"<BR>> > "<BR>> > It seems that configure made a choice of
__int64 for the Win64 package <BR>> > instead of long under linux. Any
idea how this might be solved?<BR>> > I have also attached the output with
the -E option in the attachment <BR>> > err.txt for your
reference.<BR>> > BTW, I tried to manually change<BR>> > typedef
__int64 MPI_Aint;<BR>> > to<BR>> > typedef long MPI_Aint;<BR>>
> and then, I got:<BR>> > gcc -I /c/MPICH2/include/ test.c -L
/c/MPICH2/lib/ -lmpi <BR>> > test.c: In function 'main':<BR>> >
test.c:15: warning: incompatible implicit declaration of built-in <BR>> >
function 'printf'<BR>> >
C:/Users/ting/AppData/Local/Temp/ccsAr9gj.o:test.c:(.text+0x22): <BR>> >
undefined reference to `_MPI_Init'<BR>> >
C:/Users/ting/AppData/Local/Temp/ccsAr9gj.o:test.c:(.text+0x36): <BR>> >
undefined reference to `_MPI_Comm_rank'<BR>> > collect2: ld returned 1
exit status<BR>> ><BR>> > or the following for using g++:<BR>>
><BR>> > $ g++ -I /c/MPICH2/include/ test.c -L /c/MPICH2/lib/
-lmpi<BR>> >
C:/Users/ting/AppData/Local/Temp/ccPO9opx.o:test.c:(.text+0x22): <BR>> >
undefined reference to `_MPI_Init'<BR>> >
C:/Users/ting/AppData/Local/Temp/ccPO9opx.o:test.c:(.text+0x36): <BR>> >
undefined reference to `_MPI_Comm_rank'<BR>> > collect2: ld returned 1
exit status<BR>> ><BR>> <BR>> You said that you downloaded the
binary distribution, correct? I have no <BR>> experiences with MPICH2 on
Windows<BR>> but I would suspect that the libraries were build with
Microsofts C/C++ <BR>> compiler cl and on Win64 the MingGW gcc<BR>>
compiler and cl are not compatible. __int64 is a Microsoft specific <BR>>
extension to C/C++
(http://msdn.microsoft.com/en-us/library/29dh1w7z.aspx).<BR>> Also it seems
that gcc does some sort of name-mangling (adding an <BR>> underscore to the
function name). This is rather strange<BR>> for a C compiler...<BR>>
<BR>> Probably you'r right that its a gcc 4.3 issue. Maybe some else has more
<BR>> insight into this.<BR>> <BR>> Interestingly he doesn't say that
he can't find libmpi.a. Are you sure <BR>> that it is not there?<BR>>
<BR>> BTW: typedef long MPI_Aint might be a problem because sizeof(long) = 4
<BR>> on Windows at least with the Microsoft compiler. Don't know
what<BR>> gcc does in this situation.<BR>> <BR>> Dorian<BR>>
<BR>> ><BR>> ><BR>> > Thanks again.<BR>> ><BR>> >
T.<BR>> ><BR>> ><BR>> > > Date: Sun, 4 Jan 2009 18:29:23
+0100<BR>> > > From: ddkrause@uni-bonn.de<BR>> > > To:
mpich-discuss@mcs.anl.gov<BR>> > > Subject: Re: [mpich-discuss]
question regarding compiling/linking <BR>> > under MingW (MPICH2
1.08)<BR>> > ><BR>> > > Hi<BR>> > ><BR>> > >
ting lei wrote:<BR>> > > > Hi,<BR>> > > ><BR>> >
> > Sorry to bother all. I have some questions regarding using MPICH2
<BR>> > 1.08<BR>> > > > with MingW<BR>> > >
><BR>> > > > I tried compile MPICH2 1.08 on two different
machines, and have met<BR>> > > > different problems. I was
wondering if someone with a lot experience<BR>> > > > could help me
out here. thanks in advance.<BR>> > > ><BR>> > > > 1)
The most successful attempt was on a win32 platform, XPSP3 with<BR>> >
> > MingW+gcc3.4.5<BR>> > > > The command line I used
was:<BR>> > > > gcc -I /c/MPICH2/include/ -lmpi -L/c/MPICH2/lib/
test.c<BR>> > > > and I get the following error:<BR>> > >
> C:/DOCUME~1/ting/LOCALS~1/Temp/cc40AD3K.o:test.c:(.text+0x38):<BR>> >
> > undefined reference to `MPI_Init'<BR>> > > >
C:/DOCUME~1/ting/LOCALS~1/Temp/cc40AD3K.o:test.c:(.text+0x4b):<BR>> > >
> undefined reference to `MPI_Comm_rank'<BR>> > > > collect2: ld
returned 1 exit status<BR>> > ><BR>> > > Could you try<BR>>
> ><BR>> > > gcc -I /c/MPICH2/include/ test.c -L/c/MPICH2/lib/
-lmpi<BR>> > ><BR>> > > Since your testprogram depends on the
mpi library you need to specify<BR>> > > the library after your program
because the linker goes from left to <BR>> > right.<BR>> > >
><BR>> > > > It seems that the library file libmpi.a is corrected
specified,<BR>> > > > because if I change it to -lmpi1 it will
report<BR>> > > >
c:\mingw\bin\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe:<BR>>
> > > cannot find -lmpi1<BR>> > > > collect2: ld returned 1
exit status<BR>> > > ><BR>> > > ><BR>> > > >
2) My less successful attempt was on a Win64 (Vista64) platform with<BR>>
> > > MingW + gcc4.3:<BR>> > > > I tried installing the
mpich2-1.0.8-win-x86-64.msi. but<BR>> > > > a) after the
installation, I couldn't find libmpi.a in MPICH2\lib<BR>> > > >
folder as I was able to in case 1).b) when I am compiling the toy <BR>> >
test<BR>> > > > program, I get many errors like this:<BR>> >
> ><BR>> > > > In file included from test.c:1:<BR>> >
> > c:/MPICH2/include/mpi.h:334: error: expected '=', ',', ';', 'asm'
or<BR>> > > > '__attribute__' before 'MPI_Aint'<BR>> > >
><BR>> > > > Is this a gcc4.x problem?<BR>> > ><BR>>
> > Did you take a look at mpi.h line 334? On Linux I can see typedef
long<BR>> > > MPI_Aint; . Could you compile with the -E flag to see the
preprocessor<BR>> > > output? Maybe something is overwriting
long?<BR>> > ><BR>> > > ><BR>> > > >
Best<BR>> > > ><BR>> > > > T<BR>> > >
><BR>> > > ><BR>> > > > <BR>> >
------------------------------------------------------------------------<BR>>
> > > From: jayesh@mcs.anl.gov<BR>> > > > To:
leitingl@hotmail.com<BR>> > > > CC:
mpich-discuss@mcs.anl.gov<BR>> > > > Subject: RE: [mpich-discuss]
(no subject) - mingw<BR>> > > > Date: Tue, 2 Dec 2008 13:34:18
-0600<BR>> > > ><BR>> > > > Hi,<BR>> > > >
You could try installing MPICH2 on windows (from the installer<BR>> > >
> available at<BR>> > > > <BR>> >
http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=downloads)
<BR>> ><BR>> > > > and compile your code and link with the gcc
libs (*.a) provided with<BR>> > > > the installation (MPICH2\lib
directory).<BR>> > > ><BR>> > > > Regards,<BR>> >
> > Jayesh<BR>> > > ><BR>> > > > <BR>> >
------------------------------------------------------------------------<BR>>
> > > *From:* mpich-discuss-bounces@mcs.anl.gov<BR>> > > >
[mailto:mpich-discuss-bounces@mcs.anl.gov] *On Behalf Of *ting lei<BR>> >
> > *Sent:* Tuesday, December 02, 2008 1:31 PM<BR>> > > >
*To:* mpich-discuss@mcs.anl.gov<BR>> > > > *Subject:*
[mpich-discuss] (no subject)<BR>> > > ><BR>> > > >
Hi,<BR>> > > ><BR>> > > > This might be a newbie
question.<BR>> > > > I see in this thread that people can compile
MPICH2 with MingW. I <BR>> > tried that with MingW (gcc 4.3 and 3.4x)
several times but<BR>> > > > I was never able to get past the
./configure step.<BR>> > > > /"I have compiled a C executable using
the MPICH2 Windows <BR>> > libraries and //MinGW./"<BR>> > > >
Could someone please give me some pointers how to compile such an <BR>> >
executable?<BR>> > > > More specifically, do I have to compile
MPICH2 itself from source <BR>> > using MinGW then use some program such
as mpicc??<BR>> > > > or should I just compile a regular c program
and run it with <BR>> > mpiexec.exe ?<BR>> > > > If I were to
compile MPICH2 itself with MingW, what other packages <BR>> > do I need
except the latest version of MingW?<BR>> > > ><BR>> > >
><BR>> > > > Many thanks for your help<BR>> > >
><BR>> > > ><BR>> > > ><BR>> > >
><BR>> > > >
<http://clk.atdmt.com/MRT/go/127032869/direct/01/><BR>> > > >
<BR>> >
------------------------------------------------------------------------<BR>>
> > > It’s the same Hotmail®. If by “same” you mean up to 70% faster.
Get<BR>> > > > your account now.<BR>> > > > <BR>>
>
<http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_broad1_122008><BR>>
> ><BR>> ><BR>> >
------------------------------------------------------------------------<BR>>
> Send e-mail faster without improving your typing skills. Get your <BR>>
> Hotmail® account. <BR>> >
<http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008><BR>>
<BR><BR><BR>
<HR>
Life on your PC is safer, easier, and more enjoyable with Windows Vista®. <A
href="http://clk.atdmt.com/MRT/go/127032870/direct/01/">See how </A><BR>
<HR>
Send e-mail anywhere. No map, no compass. <A
href="http://windowslive.com/oneline/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_anywhere_122008">Get
your Hotmail® account now.</A><BR>
<HR>
Insert movie times and more without leaving Hotmail®. <A
href="http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd1_052009"
target=_new>See how.</A> </BODY></HTML>