I should have mentioned that I was working on Linux.
On 4/13/2015 5:34 PM, Ralph Castain wrote:
Yeah, I verified that on a new machine (Mac OSX 10.10) everything
built fine with gcc 4.9.2 - but that’s a new glibc
On Apr 13, 2015, at 4:30 PM, John Cary <mailto:c...@txcorp.com>&
Biomedical | Ryan Novosielski - Senior Technologist
|| \\ and Health | novos...@rutgers.edu <mailto:novos...@rutgers.edu>-
973/972.0922 (2x0922)
|| \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark
`'
On Apr 13, 2015, at 17:21, John Cary <mailto:c...@txcorp
I am seeing:
Making all in tools/ompi_info
make[2]: Entering directory
`/scr_devlinux/cary/vorpalall/builds/openmpi-1.8.4/static/ompi/tools/ompi_info'
CC ompi_info.o
CC param.o
CCLD ompi_info
../../../ompi/.libs/libmpi.a(strfns.o): In function `lstat64':
strfns.c:(.text+0
this?
Or in practice, must one build on a machine to use that machine's MPI?
Thx.John Cary
___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post:
http://www.open-mpi.org/comm
For cmake,
-DCMAKE_SHARED_LINKER_FLAGS:STRING=-Wl,-rpath,'$HDF5_SERSH_DIR/lib'
or
-DCMAKE_EXE_LINKER_FLAGS:STRING=-Wl,-rpath,'$HDF5_SERSH_DIR/lib'
I don't have a dog in this, but I will say that we have found supporting
Windows
to be much easier with cmake. If that is not an issue, then autot
GNU/Linux
gcc (GCC) 4.4.0 20090506 (Red Hat 4.4.0-4)
I did discover that my previous configure had a wrong value for the
--with-wrapper-ldflags argument. Now all works.
It seems that the rpath arg is something that bites me over and again.
What are your thoughts about making this automatic?
Thx.John Cary
I doubt that this is consistent
with how your build system is designed, but it works for me.
I am sending you the diff in case it helps you in any way.
BTW, I also fixed some blanks after backslashes in
contrib/Makefile.am. This is also in the attached patch.
BestJohn Cary
diff -ruN ./contrib/Ma
