Also, I recommend you do not name your library libmpi.so, since this name
is already used by Open MPI
Cheers,
Gilles
On Saturday, June 25, 2016, Jeff Squyres (jsquyres)
wrote:
> On Jun 24, 2016, at 4:39 PM, Richard C. Wagner > wrote:
> >
> > Then I try to compile the library file in 32-bit mo
On Jun 24, 2016, at 4:39 PM, Richard C. Wagner wrote:
>
> Then I try to compile the library file in 32-bit mode. The first command is:
>
> mpicc -fPIC -m32 -c libtest.c
>
> Then the second is:
>
> mpicc -shared -m32 -o libmpi.so libtest.o
>
> As you can see below, compiling the object file w
Ralph and Jeff:
Thanks for your replies to my questions about compiling a 32-bit MPI library
for Forth.
Ralph wrote:
IIRC, you would need to write a wrapper to let Forth access C-based functions, yes? You could
configure and build OMPI as a 32-bit library, and libmpi.so is C, so that isn?t an
Greetings Richard.
Yes, that certainly is unusual. :-)
Here's my advice:
- Configure Open MPI with the --disable-dlopen flag. This will slurp in all of
Open MPI's plugins into the main library, and make things considerably simpler
for you.
- Build Open MPI in a 32 bit mode -- e.g., supply C
Wow, I haven’t encountered Forth in over 20 years! Though I confess I used to
program in it myself back in my control days.
IIRC, you would need to write a wrapper to let Forth access C-based functions,
yes? You could configure and build OMPI as a 32-bit library, and libmpi.so is
C, so that isn
Hi Everyone:
I'm trying to employ MPI in an unconventional programming language, Forth, running over Debian
Linux. The Forth I have can import a Linux shared library in the .so file format and then compile
in the executable functions as externals. The question: how to do it? I'm looking to a
The -x option only applies to your application processes - it is never
applied to the OMPI processes such as the OMPI daemons (orteds). If
you built OMPI with the Intel library, then trying to pass the path to
libimf via -x will fail - your application processes will get that
library path,
mpirun -x LD_LIBRARY_PATH -host tya64 connectivity_c
complained about libimf.so (not found), just the same as without "-x
LD_LIBRARY_PATH" (tried to give the full path to the PATH with same
error)
while
# dpkg --search libimf.so
/opt/intel/fce/10.1.022/lib/libimf.so
/opt/intel/fce/10.1.022/lib/l
On Apr 13, 2009, at 12:07 PM, Francesco Pietra wrote:
I knew that but have considered it again. I wonder whether the info at
the end of this mail suggests how to operate from the viewpoint of
openmpi in compiling a code.
In trying to compile openmpi-1.3.1 on debian amd64 lenny, intels
10.1.022
I knew that but have considered it again. I wonder whether the info at
the end of this mail suggests how to operate from the viewpoint of
openmpi in compiling a code.
In trying to compile openmpi-1.3.1 on debian amd64 lenny, intels
10.1.022 do not see their librar libimf.so, which is on the unix p
If you want to find libimf.so, which is a shared INTEL library,
pass the library path with a -x on mpirun
mpirun -x LD_LIBRARY_PATH
DM
On Fri, 10 Apr 2009, Francesco Pietra wrote:
Hi Gus:
If you feel that the observations below are not relevant to openmpi,
please disregard the mes
See this FAQ entry:
http://www.open-mpi.org/faq/?category=running#intel-compilers-
static
On Apr 10, 2009, at 12:16 PM, Francesco Pietra wrote:
Hi Gus:
If you feel that the observations below are not relevant to openmpi,
please disregard the message. You have already kindly devoted so
Hi Gus:
If you feel that the observations below are not relevant to openmpi,
please disregard the message. You have already kindly devoted so much
time to my problems.
The "limits.h" issue is solved with 10.1.022 intel compilers: as I
felt, the problem was with the pre-10.1.021 version of the int
Hi Francesco
Francesco Pietra wrote:
Hi:
As failure to find "limits.h" in my attempted compilations of Amber of
th fast few days (amd64 lenny, openmpi 1.3.1, intel compilers
10.1.015) is probably (or I hope so) a bug of the version used of
intel compilers (I made with debian the same observation
Hi:
As failure to find "limits.h" in my attempted compilations of Amber of
th fast few days (amd64 lenny, openmpi 1.3.1, intel compilers
10.1.015) is probably (or I hope so) a bug of the version used of
intel compilers (I made with debian the same observations reported
for gentoo,
http://software.
15 matches
Mail list logo
