Josh and I spent some quality time on the phone today talking through
this issue. Here's some points (not in strict order):
- "--enable-static --enable-shared" (either explicit or implicit)
works fine -- it'll build both static and shared library versions of
OMPI's libraries. Unless other
On Sun, 2006-10-15 at 23:31 -0600, Josh England wrote:
> On Sat, 2006-10-14 at 09:35 -0400, Jeff Squyres wrote:
> > Given the messages from the linker and my prior mail, I'm not sure
> > that a) is possible -- it will require more poking around to know for
> > sure. b) is definitely possible s
On Sat, 2006-10-14 at 09:35 -0400, Jeff Squyres wrote:
> Given the messages from the linker and my prior mail, I'm not sure
> that a) is possible -- it will require more poking around to know for
> sure. b) is definitely possible simply by using --enable-static and
> and then using "mpicc" (
On Sat, 2006-10-14 at 09:35 -0400, Jeff Squyres wrote:
> - What exactly is your intent: a) do you want 100% static executables
> (to include the normal Linux system libraries), b) do you just want
> to avoid having to set LD_LIBRARY_PATH for some of the esoteric
> libraries such as libmpi, li
It also depends on what exactly you mean by "static binaries" (see
below).
To fill in the background for those on the list, we had some prior
off-list e-mail about static builds where I said:
-
Keep in mind that "--disable-shared --enable-static" on OMPI's
configure line refers to how
Shouldn't mpicc always link system libraries (like -ldl and -lsysfs)
dynamically?
Scott Weitzenkamp
SQA and Release Manager
Server Virtualization Business Unit
Cisco Systems
> -Original Message-
> From: users-boun...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of Josh E
