Something else interesting that I just discovered. If I do this, I have
the problem:
rpmbuild --rebuild -bb path/to/openmpi-1.6-2.src.rpm
However, if I do an "rpm -i path/to/openmpi-1.6-2.src.rpm", and then do
very-similar rpmbuild syntax, it puts everything where I want it:
rpmbuild -bb
Is there an easy way with the .spec file and the rpmbuild command, for
me to override the path the OpenMPI RPM installs into, in /opt?
Basically, I'm already doing something like this:
rpmbuild --rebuild --define 'install_in_opt 1' --define '_name
fsl_openmpi_intel' --define 'name
Damien,
Thank you very much for your prompt reply.
Your comments helped me to find the proper settings. The thing that was
missing was CLR.
For other users that might have the same problem, here is the
configuration that worked (at least for Windows XP, VS2008 Pro):
//
// Configuration
On 6/26/2012 9:20 AM, Jeff Squyres wrote:
Sorry, this looks like an application issue -- i.e., the linker error you're
getting doesn't look like it's coming from Open MPI. Perhaps it's a missing
application/middleware library.
More specifically, you can take the mpif90 command that is being
Dear Syed,
Why do you think it is related to MPI?
You seem to be compiling the COSMO model, which depends on netcdf lib, but
the symbols are not passed to linker by some reason. Two main reasons are:
(1) the library linking flag is missing (check you have something like
-lnetcdf -lnetcdff in
Sorry, this looks like an application issue -- i.e., the linker error you're
getting doesn't look like it's coming from Open MPI. Perhaps it's a missing
application/middleware library.
More specifically, you can take the mpif90 command that is being used to
generate these errors and add
Dear All
I am getting following error while compilation of an application. Seems
like something related to netcdf and mpif90. Although I have compiled
netcdf with mpif90 option, dont why this error is happening. Any hint would
be highly appreciated.
Really fast off the top of my head, LNK4248 and LNK2020 are
Microsoft-specific C++/CLI warning for managed C++. Are you intending
to use managed C++ in your app? That can do funny things to linker symbols.
Also, you might need to have all three of OMPI_IMPORTS, OPAL_IMPORTS and
ORTE_IMPORTS
