On Sep 26, 2005, at 4:20 PM, Roland Dreier wrote:
[It's somewhat annoying to have to subscribe to de...@open-mpi.org
just to be able to send patches, but oh well...]
It's even more annoying to be deluged with SPAM ;). We (the LAM
developers) used to try to keep our mailing lists as open as
On Mon, 2005-09-26 at 20:09 +, Ferris McCormick wrote:
> On Mon, 2005-09-26 at 14:59 +, Ferris McCormick wrote:
> > On Fri, 2005-09-16 at 11:35 -0500, Brian Barrett wrote:
> > > On Sep 16, 2005, at 8:44 AM, Ferris McCormick wrote:
> > >
> > > > ==
>
Thanks muchly for tracking this down! I'm working on the fixes right
now; will commit shortly.
On Sep 27, 2005, at 11:59 AM, Ferris McCormick wrote:
On Mon, 2005-09-26 at 20:09 +, Ferris McCormick wrote:
On Mon, 2005-09-26 at 14:59 +, Ferris McCormick wrote:
On Fri, 2005-09-16 at
Brian> It's even more annoying to be deluged with SPAM ;). We
Brian> (the LAM developers) used to try to keep our mailing lists
Brian> as open as possible. In the end, SPAM pushed the signal to
Brian> noise ratio way too high and something had to be done.
Brian> Requiring subs
So is this an error or am I configuring wrong?
Here's my configure:
[sparkplug]~/ompi > ./configure CFLAGS=-m32 FFLAGS=-m32 CXXFLAGS=-m32
--without-threads --prefix=/home/ndebard/local/ompi
--with-devel-headers --without-gm
I've also tried adding --build=i586-suse-linux, that didn't help eit
This looks like it *might* be a libtool problem -- it's picking up the
/usr/lib64/libstdc++.so when you're compiling in 32 bit mode (and
therefore barfing).
Can you send the libtool command that immediately preceded this link
line?
As a workaround, you should be able to --disable-cxx to d
Hi Nathan, Jeff,
* Jeff Squyres wrote on Tue, Sep 27, 2005 at 09:39:59PM CEST:
> This looks like it *might* be a libtool problem -- it's picking up the
> /usr/lib64/libstdc++.so when you're compiling in 32 bit mode (and
> therefore barfing).
Yep, I think it is.
> Can you send the libtool com
Hi,
Trying to install ompi on a bproc machine with no network filesystem.
I've copied the contents of the ompi lib directory into /tmp/ompi on
each node and set my LD_LIBRARY_PATH to /tmp/ompi. However when I run
the program, I get the following error. Any suggestions on what else
I need
Hi Greg,
* Greg Watson wrote on Tue, Sep 27, 2005 at 10:27:22PM CEST:
>
> Trying to install ompi on a bproc machine with no network filesystem.
> I've copied the contents of the ompi lib directory into /tmp/ompi on
> each node and set my LD_LIBRARY_PATH to /tmp/ompi. However when I run
> th
This exact problem came up in a different context today.
This is only a side-effect of us having crummy error messages. :-(
What is happening is that OMPI is not finding its components.
Specifically, it's looking for the SDS components in this case, not
finding them, and then barfing.
Op
Yes!!! It worked:
I have the components installed in /home/gwatson/ompi_install/lib/
openmpi on the front end and in /tmp/ompi/openmpi on the nodes. The
two things I need to do are:
1. Set my LD_LIBRARY_PATH to /home/gwatson/ompi_install/lib:/tmp/ompi
so that it picks up the shared librari
11 matches
Mail list logo
