Greetings, Jeff.
Sure, I could see that. But I'm trying to run on a locally mounted
filesystem in this case. I may need to run make in debug mode and see what
it thinks is out of date. See if you guys can help me track down the
dependency problem.
-Sean
--
Sean Ahern
Computational Engine
Yep, that's it.
-Sean
--
Sean Ahern
Computational Engineering International
919-363-0883
On Thu, Sep 1, 2016 at 1:04 PM, Jeff Squyres (jsquyres)
wrote:
> That's odd -- I've never seen this kind of problem happen on a
> locally-mounted filesystem.
>
> Just to make
hings going again.
Sorry for the noise completely unrelated to OpenMPI!
-Sean
--
Sean Ahern
Computational Engineering International
919-363-0883
On Thu, Sep 1, 2016 at 1:24 PM, Jeff Squyres (jsquyres)
wrote:
> Ok, weird. Try running the process again (untar, configure, make) but use
>
tolerance
> level for "ick" in a VCS. :-)
>
Not a bad idea! I may end up implementing precisely this for our work.
-Sean
--
Sean Ahern
Computational Engineering International
919-363-0883
___
users mailing li
quot;, as well
as OPAL_PREFIX pointing to …"openmpi-2.0.1".
Any thoughts about how I can try to tease out what's going wrong here?
-Sean
--
Sean Ahern
Computational Engineering International
919-363-0883
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Gilles,
You described the problem exactly. I think we were able to nail down a
solution to this one through judicious use of the -rpath $MPI_DIR/lib
linker flag, allowing the runtime linker to properly find OpenMPI symbols
at runtime. We're operational. Thanks for your help.
-Sean
--
Sean
s>, and especially here
<https://www.open-mpi.org/faq/?category=sysadmin>) seem to suggest that I
am.)
Our first test platform will be getting OpenMPI via IB working on our
cluster, where we have IB (and TCP/IP) functional and not OpenMPI. This
will be a great stand-in for a customer that
7;t the plugin
require at least runtime linking with a low-level transport library?)
-Sean
--
Sean Ahern
Computational Engineering International
919-363-0883
On Fri, Oct 28, 2016 at 3:40 PM, r...@open-mpi.org wrote:
> You don’t need any of the hardware - you just need the headers. Things
>
That's useful. Thank you.
It sounds like, as long as the component exists for OpenMPI already, it's
just a matter of compiling OpenMPI on a machine that has the headers and
libraries (with appropriate configure flags), and grabbing the individual
component from there.
-Sean
--
Sounds to me like you're missing a -ldl linker flag.
-Sean
--
Sean Ahern
Computational Engineering International
919-363-0883
On Thu, Nov 3, 2016 at 3:57 PM, Mahmood Naderan
wrote:
> Hi
> I am building scalapack with mpicc and mpifort, however this is the error
> I get:
>
Any chance this will be recorded for those who won't be able to be there
next week?
-Sean
--
Sean Ahern
Computational Engineering International
919-363-0883
On Thu, Nov 10, 2016 at 11:00 AM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> Be sure to come see us at "Op
Make sense. Thanks for making the slides available. Would you mind posting
to the list when the rest of us can get them?
-Sean
--
Sean Ahern
Computational Engineering International
919-363-0883
On Tue, Nov 15, 2016 at 10:53 AM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
>
12 matches
Mail list logo
