[MPICH] RE: [Fwd: Re: Building a ch_xxx for mpich2 under Windows]

Jayesh Krishna jayesh at mcs.anl.gov
Tue Oct 9 15:59:35 CDT 2007 

 Hi,
  The functions shown unresolved (MPIDI_CH3I_Progress*) in your email are
defined by the channel (in the case of the sock channel it is defined in
ch3/channels/sock/src/ch3_progress.c).

Regards,
Jayesh

-----Original Message-----
From: owner-mpich-discuss at mcs.anl.gov
[mailto:owner-mpich-discuss at mcs.anl.gov] On Behalf Of Jayesh Krishna
Sent: Tuesday, October 09, 2007 3:29 PM
To: 'Markus Fischer'
Cc: mpich-discuss at mcs.anl.gov
Subject: [MPICH] RE: [Fwd: Re: Building a ch_xxx for mpich2 under Windows]

 Hi,
  Did you follow the order in compiling the projects as I mentioned in my
previous email. You can look into the makewindist.bat batch file (look for
"BUILD_RELEASE" label) and follow the steps mentioned there (You need to
compile the mpich2 solution with the appropriate solution configuration as
specified in my email).


{Ref: Also note the difference in "project" and "solution" in each step
while compiling MPICH2.
>> 1) Run "cscript winconfigure.wsf --cleancode" at the command prompt 
>> to configure MPICH2.
>> 2) Replace the appropriate files in the ch3sock project.
>> 3) Build mpich2 solution using the "ch3sockRelease" configuration
>> 4) Build "mpich2s" project using the "ch3sockRelease" configuration
>> 5) Build mpich2 solution using the "Release" configuration.
>> 6) If you require fortran support, build mpich2 solution using the 
>> "fortRelease", "gfortRelease" & "sfortRelease" configuration
>>
}


Regards,
Jayesh

-----Original Message-----
From: Markus Fischer [mailto:fischer at myri.com]
Sent: Tuesday, October 09, 2007 3:23 PM
To: Jayesh Krishna
Subject: Re: [Fwd: Re: Building a ch_xxx for mpich2 under Windows]

Ok, yes it's 1.0.6 and the Solution is set to Release

Still I get the following errors:

1>------ Build started: Project: mpich2, Configuration: ch3sockRelease
1>Win32 ------ Linking...
1>   Creating library .\ch3sockRelease/mpich2.lib and object 
1>.\ch3sockRelease/mpich2.exp waitall.obj : error LNK2019: unresolved 
1>external symbol _MPIDI_CH3I_Progress referenced in
function _PMPI_Waitall
1>waitany.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_Progress waitsome.obj : error LNK2001: unresolved external 
1>symbol _MPIDI_CH3I_Progress testall.obj : error LNK2001: unresolved 
1>external symbol _MPIDI_CH3I_Progress testany.obj : error LNK2001:
1>unresolved external symbol _MPIDI_CH3I_Progress testsome.obj : error
1>LNK2001: unresolved external symbol _MPIDI_CH3I_Progress wait.obj : 
1>error LNK2001: unresolved external symbol _MPIDI_CH3I_Progress 
1>sendrecv.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_Progress sendrecv_rep.obj : error LNK2001: unresolved 
1>external symbol _MPIDI_CH3I_Progress ssend.obj : error LNK2001:
1>unresolved external symbol _MPIDI_CH3I_Progress test.obj : error
1>LNK2001: unresolved external symbol _MPIDI_CH3I_Progress 
1>request_free.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_Progress request_get_status.obj : error LNK2001:
1>unresolved external symbol _MPIDI_CH3I_Progress rsend.obj : error
1>LNK2001: unresolved external symbol _MPIDI_CH3I_Progress send.obj : 
1>error LNK2001: unresolved external symbol _MPIDI_CH3I_Progress 
1>bsendutil.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_Progress comm_disconnect.obj : error LNK2001: unresolved 
1>external symbol _MPIDI_CH3I_Progress helper_fns.obj : error LNK2001:
1>unresolved external symbol _MPIDI_CH3I_Progress recv.obj : error
1>LNK2001: unresolved external symbol _MPIDI_CH3I_Progress waitsome.obj
1>: error LNK2019: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
referenced in function _PMPI_Waitsome
1>ssend.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>wait.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>waitall.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>waitany.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>rsend.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>send.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>sendrecv.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>sendrecv_rep.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>bsendutil.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>comm_disconnect.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>helper_fns.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>recv.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3I_progress_completion_count
1>commutil.obj : error LNK2019: unresolved external symbol 
1>_MPID_VCRT_Add_ref referenced in function
_MPIR_Setup_intercomm_localcomm
1>ssend.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3_Request_destroy rsend.obj : error LNK2001: unresolved 
1>external symbol _MPIDI_CH3_Request_destroy send.obj : error LNK2001:
1>unresolved external symbol _MPIDI_CH3_Request_destroy sendrecv.obj : 
1>error LNK2001: unresolved external symbol _MPIDI_CH3_Request_destroy 
1>sendrecv_rep.obj : error LNK2019: unresolved external symbol 
1>_MPIDI_CH3_Request_destroy referenced
in function _PMPI_Sendrecv_replace
1>helper_fns.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3_Request_destroy mpir_request.obj : error LNK2001:
1>unresolved external symbol _MPIDI_CH3_Request_destroy recv.obj : error
1>LNK2001: unresolved external symbol _MPIDI_CH3_Request_destroy 
1>request_free.obj : error LNK2001: unresolved external symbol 
1>_MPIDI_CH3_Request_destroy initthread.obj : error LNK2019: unresolved 
1>external symbol _MPID_InitCompleted referenced in
function _MPIR_Init_thread
1>intercomm_create.obj : error LNK2019: unresolved external symbol 
1>_MPID_VCR_CommFromLpids
referenced in function _PMPI_Intercomm_create
1>intercomm_create.obj : error LNK2019: unresolved external symbol 
1>_MPID_PG_ForwardPGInfo referenced
in function _PMPI_Intercomm_create
1>intercomm_create.obj : error LNK2019: unresolved external symbol 
1>_MPID_GPID_ToLpidArray referenced
in function _PMPI_Intercomm_create
1>intercomm_create.obj : error LNK2019: unresolved external symbol 
1>_MPID_GPID_GetAllInComm
referenced in function _PMPI_Intercomm_create
1>sockmtp.lib(sock.obj) : error LNK2019: unresolved external symbol 
1>_WriteCurrentDataAndLogEvent
referenced in function _MPIDU_Sock_init
1>sockmtp.lib(sock.obj) : error LNK2001: unresolved external symbol 
1>_g_pRLOG lib/mpich2.dll : fatal error LNK1120: 11 unresolved externals 
1>Build log was saved at
"file://c:\cygwin\home\markus\mpich2-mx-windows\mpich2-1.0.6\ch3sockRelease\
BuildLog.htm"
1>mpich2 - 50 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 5 up-to-date, 0 skipped ==========


Markus

--------


Jayesh Krishna wrote:
> Hi,
>  There should be a "Release" configuration for the mpich2 solution 
> (Look in "Solution configurations" drop box in VS).
> 
> (PS: I am hoping you are using the source in 1.0.6 for your build)
> 
> Regards,
> Jayesh
> -----Original Message-----
> From: Markus Fischer [mailto:fischer at myri.com]
> Sent: Tuesday, October 09, 2007 2:57 PM
> To: Jayesh Krishna
> Cc: mpich2-maint at mcs.anl.gov
> Subject: Re: [Fwd: Re: Building a ch_xxx for mpich2 under Windows]
> 
> There seems to be no "Release" option. All options involve CH3xxx options.
> After also building pmi and smpd_util I get the following errors:
> 
> 4>------ Build started: Project: mpich2, Configuration: ch3sockRelease
> 4>Win32 ------ Linking...
> 4>dbgd.lib(msgprint.obj) : warning LNK4075: ignoring 
> 4>'/EDITANDCONTINUE' due
> to '/OPT:ICF' specification
> 4>   Creating library .\ch3sockRelease/mpich2.lib and object 
> 4>.\ch3sockRelease/mpich2.exp LINK : warning LNK4098: defaultlib 
> 4>'LIBCMTD' conflicts with use of other libs; use
> /NODEFAULTLIB:library
> 4>waitall.obj : error LNK2019: unresolved external symbol 
> 4>_MPIDI_CH3I_Progress referenced in
> function _PMPI_Waitall
> 4>waitany.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_Progress waitsome.obj : error LNK2001: unresolved 
> 4>external symbol _MPIDI_CH3I_Progress testall.obj : error LNK2001:
> 4>unresolved external symbol _MPIDI_CH3I_Progress testany.obj : error
LNK2001:
> 4>unresolved external symbol _MPIDI_CH3I_Progress testsome.obj : error
> 4>LNK2001: unresolved external symbol _MPIDI_CH3I_Progress wait.obj : 
> 4>error LNK2001: unresolved external symbol _MPIDI_CH3I_Progress 
> 4>sendrecv.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_Progress sendrecv_rep.obj : error LNK2001: unresolved 
> 4>external symbol _MPIDI_CH3I_Progress ssend.obj : error LNK2001:
> 4>unresolved external symbol _MPIDI_CH3I_Progress test.obj : error
> 4>LNK2001: unresolved external symbol _MPIDI_CH3I_Progress 
> 4>request_free.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_Progress request_get_status.obj : error LNK2001:
> 4>unresolved external symbol _MPIDI_CH3I_Progress rsend.obj : error
> 4>LNK2001: unresolved external symbol _MPIDI_CH3I_Progress send.obj : 
> 4>error LNK2001: unresolved external symbol _MPIDI_CH3I_Progress 
> 4>bsendutil.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_Progress comm_disconnect.obj : error LNK2001: unresolved 
> 4>external symbol _MPIDI_CH3I_Progress helper_fns.obj : error LNK2001:
> 4>unresolved external symbol _MPIDI_CH3I_Progress recv.obj : error
> 4>LNK2001: unresolved external symbol _MPIDI_CH3I_Progress 
> 4>waitsome.obj
> 4>: error LNK2019: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> referenced in function _PMPI_Waitsome
> 4>ssend.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>wait.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>waitall.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>waitany.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>rsend.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>send.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>sendrecv.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>sendrecv_rep.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>bsendutil.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>comm_disconnect.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>helper_fns.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>recv.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3I_progress_completion_count
> 4>commutil.obj : error LNK2019: unresolved external symbol 
> 4>_MPID_VCRT_Add_ref referenced in function
> _MPIR_Setup_intercomm_localcomm
> 4>ssend.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3_Request_destroy rsend.obj : error LNK2001: unresolved 
> 4>external symbol _MPIDI_CH3_Request_destroy send.obj : error LNK2001:
> 4>unresolved external symbol _MPIDI_CH3_Request_destroy sendrecv.obj : 
> 4>error LNK2001: unresolved external symbol _MPIDI_CH3_Request_destroy 
> 4>sendrecv_rep.obj : error LNK2019: unresolved external symbol 
> 4>_MPIDI_CH3_Request_destroy referenced
> in function _PMPI_Sendrecv_replace
> 4>helper_fns.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3_Request_destroy mpir_request.obj : error LNK2001:
> 4>unresolved external symbol _MPIDI_CH3_Request_destroy recv.obj : 
> 4>error
> 4>LNK2001: unresolved external symbol _MPIDI_CH3_Request_destroy 
> 4>request_free.obj : error LNK2001: unresolved external symbol 
> 4>_MPIDI_CH3_Request_destroy initthread.obj : error LNK2019:
> 4>unresolved external symbol _MPID_InitCompleted referenced in
> function _MPIR_Init_thread
> 4>intercomm_create.obj : error LNK2019: unresolved external symbol 
> 4>_MPID_VCR_CommFromLpids
> referenced in function _PMPI_Intercomm_create
> 4>intercomm_create.obj : error LNK2019: unresolved external symbol 
> 4>_MPID_PG_ForwardPGInfo referenced
> in function _PMPI_Intercomm_create
> 4>intercomm_create.obj : error LNK2019: unresolved external symbol 
> 4>_MPID_GPID_ToLpidArray referenced
> in function _PMPI_Intercomm_create
> 4>intercomm_create.obj : error LNK2019: unresolved external symbol 
> 4>_MPID_GPID_GetAllInComm
> referenced in function _PMPI_Intercomm_create
> 4>lib/mpich2.dll : fatal error LNK1120: 9 unresolved externals Build 
> 4>log was saved at
> "file://c:\cygwin\home\markus\mpich2-mx-windows\mpich2-1.0.6\ch3sockRe
> lease\
> BuildLog.htm"
> 4>mpich2 - 73 error(s), 2 warning(s)
> ========== Build: 0 succeeded, 1 failed, 2 up-to-date, 3 skipped 
> ==========
> 
> 
> 
> Any comment would be appreciated.
> 
> Markus
> 
> Jayesh Krishna wrote:
>>  Hi,
>>   The ch3sock project contains both the ADI routines and the sock 
>> channel routines. So as David suggested the easiest way to start off 
>> is replacing the files in the ch3sock project.
>>   I am assuming you are using the project & solution files from the 
>> latest source available (1.0.6). Follow the steps below to build the
>> MPICH2 suite if you are building from the Visual Studio Dev 
>> interface,
>>
>> 1) Run "cscript winconfigure.wsf --cleancode" at the command prompt 
>> to configure MPICH2.
>> 2) Replace the appropriate files in the ch3sock project.
>> 3) Build mpich2 solution using the "ch3sockRelease" configuration
>> 4) Build "mpich2s" project using the "ch3sockRelease" configuration
>> 5) Build mpich2 solution using the "Release" configuration.
>> 6) If you require fortran support, build mpich2 solution using the 
>> "fortRelease", "gfortRelease" & "sfortRelease" configuration
>>
>>   You can also build MPICH2 from the command prompt by following the 
>> directions in the windows developer's guide,
>>
>> 1) Run "cscript winconfigure.wsf --cleancode" at the command prompt 
>> to configure MPICH2.
>> 2) Replace the appropriate files in the ch3sock project.
>> 3) Run "makewindist --with-curdir" at the command prompt. (The batch 
>> file makewindist.bat executes the steps mentioned above)
>>
>>
>>  Let us know if you need any further assistance.
>>
>> Regards,
>> Jayesh
>>
>> -----Original Message-----
>> From: Markus Fischer [mailto:fischer at myri.com]
>> Sent: Monday, October 08, 2007 2:11 PM
>> To: 'Jayesh Krishna'
>> Subject: [Fwd: Re: Building a ch_xxx for mpich2 under Windows]
>>
>> actually the ch_mx I am trying to build is ADI device and not part of
ch3.
>>
>> I think using the ch3sock framework is not a good start.
>>
>> please advise,
>> Markus
>>
>> -------- Original Message --------
>> Subject: Re: Building a ch_xxx for mpich2 under Windows
>> Date: Mon, 08 Oct 2007 19:53:27 +0200
>> From: Markus Fischer <fischer at myri.com>
>> To: 'Jayesh Krishna' <jayesh at mcs.anl.gov>
>> References: <470665CF.3060902 at myri.com> 
>> <Pine.LNX.4.58.0710072152450.1811 at harley.mcs.anl.gov>
>> <000601c809c4$62de3970$860add8c at mcs.anl.gov>
>>
>> actually, when linking it complains about missing the common 
>> functions like _MPI_Init, _MPI_Finalize et al so I assume I need to 
>> build the general part as well.
>>
>> A pointer which project to build for that would be great.
>>
>> thanks, Markus
>>
>>
>> -------------
>>
>> Ok, let's see where we are...
>>
>> I did the steps David suggested and I get a ch3sockd.lib file under 
>> the lib directory.
>>
>> Is that all I need for building/linking the cpi example? I assume I 
>> just need to change the filename to mpi.lib or something similar.
>>
>> Or are there other projects / libs involved as well? A confirmation 
>> of David's suggestion would be good.
>>
>> Of course one to add is the MX library itself.
>>
>> thanks again,
>> Markus
>>
>>
>> Rajeev Thakur wrote:
>>> Markus,
>>>        Jayesh Krishna is our new Windows person. He can help you 
>>> with Windows-related questions.
>>>
>>> Rajeev
>>>  
>>>
>>>> -----Original Message-----
>>>> From: David Ashton [mailto:ashton at mcs.anl.gov]
>>>> Sent: Sunday, October 07, 2007 11:45 PM
>>>> To: Markus Fischer
>>>> Cc: mpich2-maint at mcs.anl.gov
>>>> Subject: Re: Building a ch_xxx for mpich2 under Windows
>>>>
>>>> Markus,
>>>>
>>>> I would try this:
>>>> 1) Download and unzip the source distribution.
>>>> 2) Run "winconfigure.wsf --cleancode" from the untarred directory.
>>>> 3) Bring up mpich2.sln in the Developer Studio.
>>>> 4) Replace all the files in the ch3sock project with your ch_mx files.
>>>> 5) Build the ch3sock target.
>>>>
>>>> -David Ashton
>>>>
>>>> On Fri, 5 Oct 2007, Markus Fischer wrote:
>>>>
>>>>> hi David,
>>>>>
>>>>> I am trying to bring our ch_mx device to build under Windows :)
>>>>>
>>>>> I did not find details in this document:
>>>>>         ftp://ftp.mcs.anl.gov/pub/mpi/mpich2-doc-windev.pdf
>>>>>
>>>>> What I would like to do is to open/change the mpich2.sln and make 
>>>>> it possible to build the ch_mx device (no ch3).
>>>>>
>>>>> However, I am missing some basics on how to modify the
>>>> build process.
>>>>> All I have is a bunch of files we need for the ch_mx device but I 
>>>>> don't have a good start on how to integrate it into
>>>> the mpich2.sln
>>>>> Any pointers for a start?
>>>>>
>>>>> thanks, Markus
>>>>>
>>>>>
>>
>>
>>
> 
> 
>

More information about the mpich-discuss mailing list