Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Linking failure on Windows
From: Gib Bogle (g.bogle_at_[hidden])
Date: 2012-10-02 02:25:55

They don't make any difference. I had them in, but dropped them when I found that the mpicc build didn't need them.

From: users-bounces_at_[hidden] [users-bounces_at_[hidden]] on behalf of Damien Hocking [damien_at_[hidden]]
Sent: Tuesday, 2 October 2012 7:21 p.m.
To: Open MPI Users
Subject: Re: [OMPI users] Linking failure on Windows

There's two imports missing from there, OPAL_IMPORTS and ORTE_IMPORTS.
That might be part of it.


On 01/10/2012 10:20 PM, Gib Bogle wrote:
> I guess it's conceivable that one of these Sundials include files is
> doing something:
> #include <cvode/cvode.h> /* prototypes for CVODE
> fcts. */
> #include <nvector/nvector_parallel.h> /* definition of N_Vector and
> macros /
> #include <sundials/sundials_types.h> /* definition of realtype /
> #include <sundials/sundials_math.h> /* definition of EXP */
> I am a complete beginner with Sundials, so I have no idea how it might
> interfere with the preprocessor definitions.
> Here is the compile command line from VS:
> /O2 /Ob2 /I "E:\sundials-2.5.0\include" /I "E:\Sundials-Win32\include"
> /I "c:\Program Files (x86)\OpenMPI_v1.6.2-win32\include" /D "WIN32" /D
> /D "CMAKE_INTDIR=\"Release\"" /D "_MBCS" /FD /MD
> /Fo"cvAdvDiff_non_p.dir\Release\\"
> /Fd"E:\Sundials-Win32\examples\cvode\parallel\Release/cvAdvDiff_non_p.pdb"
> /W3 /c /TC /errorReport:prompt
> Gib
> On 2/10/2012 5:06 p.m., Damien Hocking wrote:
>> So mpicc builds it completely? The only thing I can think of is look
>> closely at both the compile and link command lines and see what's
>> different. It might be going sideways at the compile from something
>> in an include with a preprocessor def.
>> Damien
> _______________________________________________
> users mailing list
> users_at_[hidden]

users mailing list