Okay, I tracked this silliness down. On odin, my platform file builds both
shared and static. It appears that mpicc in that situation defaults to picking
the static build, and so I wind up with a static executable. This behavior was
unexpected - I thought we would default to dynamic, but support
Sure - I can do that.
On Oct 30, 2012, at 11:29 AM, Edgar Gabriel wrote:
> glad to hear that. However, since we are also having the problem with
> the lustre-fs module for static builds, I think it would still make
> sense to disable fs/lustre/ for 1.7.0
>
> Edgar
>
> On 10/30/2012 12:34 PM, R
glad to hear that. However, since we are also having the problem with
the lustre-fs module for static builds, I think it would still make
sense to disable fs/lustre/ for 1.7.0
Edgar
On 10/30/2012 12:34 PM, Ralph Castain wrote:
> I hate odin :-(
>
> FWIW: it all works fine today, no matter how I
I hate odin :-(
FWIW: it all works fine today, no matter how I configure it. No earthly idea
what happened.
Ignore these droids
On Oct 30, 2012, at 7:28 AM, Edgar Gabriel wrote:
> ok, so a couple of things.
>
> I still think it is the same issue that I observed 1-2 days ago. Could
> you
ok, so a couple of things.
I still think it is the same issue that I observed 1-2 days ago. Could
you try to remove the fs/lustre component from your compilation, e.g. by
adding an .ompi_ignore file into that directory, and see whether this
fixes the issue?
I tried on my machine (no lustre, no ib
ok, I'll look into this. I noticed a problem with static builds on
lustre file systems recently, and I was wandering whether its the same
issue or not. But I'll check what's going on.
THanks
Edgar
On 10/30/2012 7:22 AM, Ralph Castain wrote:
> No to Lustre, and I didn't build static
>
> I'm not s
No to Lustre, and I didn't build static
I'm not sure what, if any, parallel file system might be present. In the case
that works, I just built with no configure args other than prefix. ompi_info
shows both romio and mpio built, but nothing more about what support they built
internally.
On Oct
Ralph,
just out curiosity: is there a lustre file system on the machine and is
this a static build ?
Thanks
Edgar
On 10/29/2012 9:17 PM, Ralph Castain wrote:
> Hmmm...I added that directory and tried this on odin (which is an IB-based
> machine). Any MPI proc segfaults:
>
> Core was generated
Hmmm...I added that directory and tried this on odin (which is an IB-based
machine). Any MPI proc segfaults:
Core was generated by `./hello'.
Program terminated with signal 11, Segmentation fault.
w#0 _sysio_p_validate (pno=0x0, intnt=0x0, path=0x0) at src/inode.c:574
574 src/inode.c: No suc
I'm sorry to add one more thing to the list, but beyond this file, it
looks like also the entire ompi/mca/common/verbs/ directory is also
missing in the 1.7 branch, but is required to compile the bcoll
framework. It is there in the trunk, but missing in the 1.7 branch...
Thanks
Edgar
On 10/26/2
Okay, I'll fix for tonights tarball.
Thanks!
On Oct 26, 2012, at 3:28 PM, "Shamis, Pavel" wrote:
> There is a bug in makefile. The file existing in svn, but it is not listed in
> the Makefile.am. As a result, it wasn't pulled to the tarball.
>
> Pavel (Pasha) Shamis
> ---
> Computer Science R
There is a bug in makefile. The file existing in svn, but it is not listed in
the Makefile.am. As a result, it wasn't pulled to the tarball.
Pavel (Pasha) Shamis
---
Computer Science Research Group
Computer Science and Math Division
Oak Ridge National Laboratory
On Oct 26, 2012, at 2:33 PM,
12 matches
Mail list logo
