No worries. It's good to see that it compiles.
Damien
On 02/10/2012 2:25 PM, Gib Bogle wrote:
Hi Shiqing,
Your post made me realize my mistake! I was thinking only of the
preprocessor definitions for compiling cvAdvDiff_non_p.c, forgetting
about the previously built library sundials_nvecpa
half of
Damien Hocking [dam...@khubla.com]
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.
Damien
On 01/10/2012 10:20 PM, Gib B
hem when I found
that the mpicc build didn't need them.
Gib
From: users-boun...@open-mpi.org [users-boun...@open-mpi.org] on behalf of
Damien Hocking [dam...@khubla.com]
Sent: Tuesday, 2 October 2012 7:21 p.m.
To: Open MPI Users
Subject: Re: [OMPI users]
en-mpi.org [users-boun...@open-mpi.org] on behalf of
Damien Hocking [dam...@khubla.com]
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
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.
Damien
On 01/10/2012 10:20 PM, Gib Bogle wrote:
> I guess it's conceivable that one of
There's two imports missing from there, OPAL_IMPORTS and ORTE_IMPORTS.
That might be part of it.
Damien
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 /* prototypes for CVODE
fcts.
I guess it's conceivable that one of these Sundials include files is doing
something:
#include /* prototypes for CVODE fcts. */
#include /* definition of N_Vector and macros /
#include /* definition of realtype /
#include/* definition of EXP */
I am a complete begin
Before I added OMPI_IMPORTS there were 8 errors, so it did help.
Here is the link command in VS 2005:
/OUT:"E:\Sundials-Win32\examples\cvode\parallel\Release\cvAdvDiff_non_p.exe"
/VERSION:0.0 /INCREMENTAL:NO /NOLOGO /LIBPATH:"c:\Program Files
(x86)\OpenMPI_v1.6.2-win32\lib" /MANIFEST
/MANIFES
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
On 01/10/2012 9:57 PM, Gib Bogle wrote:
H
Hi Damien,
I've checked and double-checked, and I can't see anything not 32-bit. In fact
my VS2005 only knows about 32-bit.
I just tested copying the source code with appropriate include directories to
another directory and built the executable successfully with mpicc. But I can't
see that
Gib,
If you have OMPI_IMPORTS set that usually removes those symbol errors.
Are you absolutely sure you have everything set to 32-bit in Visual Studio?
Damien
On 01/10/2012 7:55 PM, Gib Bogle wrote:
I am building the Sundials examples, with MS Visual Studio 2005
version 8 (i.e. 32-bit) on W
I am building the Sundials examples, with MS Visual Studio 2005 version 8 (i.e.
32-bit) on Windows 7 64-bit. The OpenMPI version is OpenMPI_1.6.2-win32.
All the parallel examples fail with the same linker errors. I have added the
preprocessor definitions OMPI_IMPORTS, OPAL_IMPORTS and ORTE_IMPO
12 matches
Mail list logo
