I am traveling all this week and so don't know when I can take a look, but
will try.
-Paul
On Mon, Mar 6, 2017 at 7:40 PM, r...@open-mpi.org wrote:
> I’m not sure what could be going on here. I take it you were able to run
> this example for the 2.0 series under this environment, yes? This code
I’m not sure what could be going on here. I take it you were able to run this
example for the 2.0 series under this environment, yes? This code hasn’t
changed since that release, so I’m not sure why it would be failing to resolve
symbols now.
> On Mar 6, 2017, at 2:22 PM, Paul Hargrove wrote:
Thanks Paul. Actually, all .c files are required to include pmix_config.h at
the very beginning of the file, before anything else. Sounds like some files
are missing it, so we’ll have to go back and fix those.
> On Mar 6, 2017, at 2:35 PM, Paul Hargrove wrote:
>
> Ralph,
>
> I found a couple
2.1.0rc2 tarball on NetBSD7/amd64.
Configured with only --prefix=... and --disable-mpi-fortran
To get past the lack of a struct timeval definition required a small source
change in a previous email.
Once past that, I can build Open MPI and compile the examples.
However, I cannot run them.
Output
Ralph,
I found a couple issues with PMIX in the 2.2.0rc2 tarball.
However, I am providing a proper fix for one and a sub-standard fix for the
other.
The following short patch resolves the build errors with "unknown type name
'pid_t'" on (so far at least) FreeBSD when compiling
opal/mca/pmix/pmix1
RC2 tarball for 2.1.0 configured with only --prefix=...
and --enable-mca-no-build=patcher
I don't have time to dig right now:
$ mpirun -mca btl sm,self -np 2 examples/ring_c
[openbsd-i386:95593] *** Process received signal ***
---
Hi,
Picking up on the thread that continued on the hwloc issue.
Jeff wrote:
> The --with-devel-headers option is really only intended for developers who
> are building Open MPI components out of tree. It is not really intended for
> end users (e.g., we don't even document it in the README file)
