Link Errors when compiling OpenMPI Application on windows

Question

I keep encountering this link error when compiling my application:

error LNK2001: unresolved external symbol "public: __cdecl MPI::Comm::Comm(void)" (??0Comm@MPI@@QEAA@XZ)    E:\Users\UT1JVT\Tanoshii\Eden\Inceptor2\Inceptor2\Node.obj  Inceptor2

If I compile it twice in a row, it changes to this (probably bec of incremental linking?):

error LNK2019: unresolved external symbol "public: __cdecl MPI::Comm::Comm(void)" (??0Comm@MPI@@QEAA@XZ) referenced in function "public: __cdecl MPI::Intracomm::Intracomm(struct ompi_communicator_t *)" (??0Intracomm@MPI@@QEAA@PEAUompi_communicator_t@@@Z)  E:\Users\UT1JVT\Tanoshii\Eden\Inceptor2\Inceptor2\Node.obj  Inceptor2

I have tried this in both x64 and 32bit mode with the matching MPI libraries to no avail. I have also defined: OMPI_IMPORTS, OPAL_IMPORTS and ORTE_IMPORTS (which fixed some of my previous link errors) but I still can't get rid of this one.

The offending line is:

_roleLocalComm = &MPI::COMM_WORLD.Split(_roleId,_nodeId);

If I remove this line (all code that creates comm groups), the error goes away. I have built the same source in Linux (Open MPI v1.6.5) and it works fine.

Here's the compile command:

/Zi /nologo /W3 /WX- /Od /D "_DEBUG" /D "_CONSOLE" /D "OMPI_IMPORTS" /D "OPAL_IMPORTS" /D "ORTE_IMPORTS" /D "_UNICODE" /D "UNICODE" /Gm /EHsc /RTC1 /GS /fp:precise /Zc:wchar_t /Zc:forScope /Fp"x64\Debug\testx64.pch" /Fa"x64\Debug\" /Fo"x64\Debug\" /Fd"x64\Debug\vc100.pdb" /Gd /errorReport:queue

Update: I tried stripping it down to bare bones and using mpic++ to compile it but I still get the same exact problem. Here's the command line:

mpic++ EntryPoint.cpp -showme
cl.exe EntryPoint.cpp /D "OMPI_IMPORTS" /I"C:\Program Files\OpenMPI_v1.6.2-x64\include" /TP /EHsc /link /LIBPATH:"C:\Program Files\OpenMPI_v1.6.2-x64\lib" libmpi_cxx.lib libmpi.lib libopen-pal.lib libopen-rte.lib advapi32.lib Ws2_32.lib shlwapi.lib

couldn't get it to work at first (tons of link errors) but then I realized that OMPI_IMPORTS is not defined so I edited %openmpi%/share/openmpi/mpic++-wrapper-data.txt to add /D "OMPI_IMPORTS"

Also, it might both mentioning that I was also getting a Link failure for MPI::Datatype::Free() which seems to be a known issue. I made a workaround for this by adding the following code. I imagine it won't cause me much of a problem since my datatypes won't be cleaned up until the job completes.

void MPI::Datatype::Free(void) {
}

@bob.sacamento I've added the compile command. I'm using visual studio 2010 — Mel
– Mel, Commented Jul 12, 2013 at 3:39
Sorry, not familiar with vis studio 2010. I might try rearranging the order of the libraries you're linking with. That helps with errors like these sometimes. That's all I've got. Good luck! — bob.sacamento
– bob.sacamento, Commented Jul 12, 2013 at 21:15

Community · Accepted Answer · 2017-04-13 12:53:54Z

2

To mirror what @cschwan said, MPICH actually doesn't support Windows anymore either. Support was discontinued at version 1.4.1p. Unfortunately, none of the big open source implementations have time for a lot of Windows support anymore since it's not used by too many people anymore outside the classroom and none of the developers use Windows. However, the best solution for MPI in Windows is to go directly to Microsoft. I would double check that their license will agree with whatever use you are planning before you start publishing any work based on MS-MPI though. I'm not overly familiar with how theirs works.

http://www.microsoft.com/en-us/download/details.aspx?id=36045

Here's the wiki page that explains MPICH's stance on things now:

http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Why_can.27t_I_build_MPICH_on_Windows_anymore.3F

As far as the C++ bindings go, you won't get much support on those from the big open source implementations anymore either since they've been removed from MPI. However, there are other bindings available out there. I know that Boost has some available (http://www.boost.org/doc/libs/1_54_0/doc/html/mpi.html), though I have no experience with how usable they are. There's actually an interesting discussion about this going on over on the scicomp site right now. You might weigh in if you have an opinion and some experience:

https://scicomp.stackexchange.com/questions/7978/what-features-do-users-need-from-an-mpi-c-interface

edited Apr 13, 2017 at 12:53

CommunityBot

11 silver badge

answered Jul 15, 2013 at 14:55

Wesley Bland

9,1623 gold badges50 silver badges62 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

cschwan Over a year ago

That explains why MPICH still has a download for Windows that actually links to the Microsoft site.

cschwan · Accepted Answer · 2013-07-16 13:24:36Z

1

+50

I don't know the reason for your problem, but I think you ran into unmaintained code:

OpenMPI has discontinued support for Windows, see here: http://www.open-mpi.org/software/ompi/v1.6/. You may use MPICH instead, available at http://www.mpich.org/downloads/. The link for MS Windows will redirect you to Microsoft's MS-MPI.
I also suggest to avoid the C++ bindings as they are deprecated as well. Simply use the C bindings instead.

edited Jul 16, 2013 at 13:24

answered Jul 15, 2013 at 14:29

cschwan

3,4033 gold badges26 silver badges32 bronze badges

Collectives™ on Stack Overflow

Link Errors when compiling OpenMPI Application on windows

2 Answers 2

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related