For Nathan, I presume:
XLC doesn't like the recently-added "ll" inline atomics:
"/gpfs-biou/phh1/OMPI/openmpi-master-linux-ppc64-xlc-11.1/openmpi-dev-2371-gea935df/opal/include/opal/sys/powerpc/atomic.h",
line 157.27: 1506-276 (S) Syntax error: possible missing string literal?
"/gpfs-biou/phh1/OM
The issue describe below on July 1 is still present on master as of last
night's tarball.
-Paul
On Wed, Jul 1, 2015 at 8:51 AM, Paul Hargrove wrote:
> Back in February I reported (
> http://www.open-mpi.org/community/lists/devel/2015/02/17073.php) that
> when building master on Linux with the S
I think that the issue is that "--" is interpreted to mean that
should be interpreted as a single string, but "-" is interpreted to mean
that each letter of should be interpreted individually.
This is a fairly common Linux/POSIX/GNU convention.
As for "--host" vs. "--hosts", we initially got
I think it would be good to get some hard facts here:
- is the infinipath library hijacking signal handlers?
- is the infinipath library not resetting those signal handlers when it is done?
- is there a way to make the infinipath library release its use of signal
handlers upon demand? (e.g., via
It looks like current and past PGI fortran compilers that are happy with
1.8.x and 1.10.x are unhappy with master:
/bin/sh ../../../../libtool --tag=FC --mode=compile pgf90
-DHAVE_CONFIG_H -I.
-I/scratch/scratchdirs/hargrove/OMPI/openmpi-master-linux-x86_64-pgi-14.7/openmpi-dev-2371-gea935df/om
I just tested this against the PGI 15.7 compiler and I see the same thing. It
appears that we get this error on some of the files called out in
ompi/mpi/fortran/use-mpi-f08/mpi-f-interfaces-bind.h as not having an
"easy-peasy" solution. All the other files compile just fine. I checked the
list
Yeah, my bad for being cryptic - very busy day.
The PSM team is doing some internal review of the problem and coming up with
solutions. Since this involves a product, the discussion has to go thru some
standard review and approval procedures before we can publicly comment on it.
Our hamsters ar
On Aug 26, 2015, at 11:17 AM, Ralph Castain wrote:
>
> Meantime, the proposed workaround to use the MCA param to ignore PSM should
> work.
...but only when the PSM MTL is not compiled directly into libmpi, e.g., via
using --disable-dlopen, or --enable-static (neither of which are the default,
> On Aug 26, 2015, at 8:23 AM, Jeff Squyres (jsquyres)
> wrote:
>
> On Aug 26, 2015, at 11:17 AM, Ralph Castain wrote:
>>
>> Meantime, the proposed workaround to use the MCA param to ignore PSM should
>> work.
>
> ...but only when the PSM MTL is not compiled directly into libmpi, e.g., via
On Aug 26, 2015, at 11:29 AM, Ralph Castain wrote:
>
>> ...but only when the PSM MTL is not compiled directly into libmpi, e.g., via
>> using --disable-dlopen, or --enable-static (neither of which are the
>> default, but it's worth mentioning).
>
> Is that true? If the problem lies in not “nic
It's that time of year again: it's our annual review of those with write access
to our Git repos.
The purpose is simply to trim those who are no longer active, or otherwise no
longer need write access to Open MPI repositories. We don't want people moving
to new jobs and still having write acce
Paul,
i tried PSM_RCVTHREAD=0 but it did not help
Jeff,
you did not read too much ... but my words were not quite accurate.
yes, the signal handlers are set in the library constructor.
by reading the source code, i found that can be avoided by setting
the yet undocumented IPATH_NO_BACKTRACE en
12 matches
Mail list logo
