[OMPI devel] [2.0.0rc3] build failure on ppc32 and arm

The same failure mode reported below is also occurring on a 32-bit ARM system. -Paul On Wed, Jun 15, 2016 at 6:13 PM, Paul Hargrove wrote: > With a PPC64/Fedora20/gcc-4.8.3 system configuring for "-m32": > > configure --prefix=[...] --enable-debug \ > CFLAGS=-m32

Re: [OMPI devel] [2.0.0rc3] NAG Fortran failures

com/open-mpi/ompi/pull/1295 > > Milestone was set to v2.0.1 so no PR was even issued (yet) for the v2.x > branch. > > If there is a consensus to update the milestone to v2.0.0, i ll be happy > to PR > > > Cheers, > > > Gilles > > On 6/16/2016 10:32 AM, Pau

[OMPI devel] [2.0.0rc3] regression: not enough space for shared memory-backing file

I am testing the 2.0.0rc3 tarball PLUS the patch from PR1232 to fix the dependence on 64-bit atomics. On an ARM system with only 256MB of memory, I am seeing the following failure which did NOT occur in my testing of 1.10.3rc4. $ mpirun -mca btl sm,self -np 2 examples/ring_c' [armel-jessie:03953]

Re: [OMPI devel] [2.0.0rc3] regression: not enough space for shared memory-backing file

, Paul Hargrove wrote: > I am testing the 2.0.0rc3 tarball PLUS the patch from PR1232 to fix the > dependence on 64-bit atomics. > On an ARM system with only 256MB of memory, I am seeing the following > failure which did NOT occur in my testing of 1.10.3rc4. > > > $ mpirun -

Re: [OMPI devel] v2.0.0rc4 is released

I am afraid that the rain dances might not have been effective, perhaps because July in San Francisco is already so cold and damp. My inbox is slowly accumulating sad-panda reports from my tests. I will report details when I am at a full-sized screen and keyboard. -Paul [Sent from my phone] On

[OMPI devel] [2.0.0rc4] non-critical faulres report

The following are previously reported issues that I am *not* expecting to be resolved in 2.0.0. However, I am listing them here for completeness. Known, but with later target: OpenBSD fails to build ROMIO - PR1178 exists with v2.0.1 target NAG Fortran support - PR1215 exists with v2.0.1 target K

[OMPI devel] [2.0.0rc4] dlopen_test crash with xlc

The issue reported in https://www.open-mpi.org/community/lists/devel/2016/06/19107.php is still present on both my little-endian Power8 and big-endian Power7 systems. I know Nathan had been working on this, but I've lost track of the issue and/or pr number(s). -Paul -- Paul H. Hargrove

[OMPI devel] [2.0.0rc4] check failure with Linux Studio Compilers and -m32

I have the Sun/Oracle Studio compilers installed on Linux/x86-64 systems. I test versions 12.2 and 12.4 with "-m32". I both of those builds "make check" is failing with a SEGV from dlopen_test. This is an improvement over the previous rc3, which did not build at all. >From the core file on the Stu

Re: [OMPI devel] [2.0.0rc4] dlopen_test crash with xlc

t; system and we haven't been runing 'make check'. I have another system that > has XLC 13.1.2 that I can test on as well. I'm not sure if I'll be able to > fix without Nathan's help, but I can at least try to reproduce. > > Thanks, > Josh > > > O

Re: [OMPI devel] [2.0.0rc4] non-critical faulres report

re you get the ICE when > using the -m32 option? > > Thanks, > > Howard > > > 2016-07-06 15:29 GMT-06:00 Paul Hargrove : > >> The following are previously reported issues that I am *not* expecting to >> be resolved in 2.0.0. >> However, I am listing the

Re: [OMPI devel] [2.0.0rc4] non-critical faulres report

I have a lead on a 15.10 installation with -m32 support. I will report results later. -Paul On Tue, Jul 12, 2016 at 10:29 AM, Jeff Squyres (jsquyres) < jsquy...@cisco.com> wrote: > Got it; thanks. > > > On Jul 12, 2016, at 1:00 PM, Paul Hargrove wrote: > > >

Re: [OMPI devel] [2.0.0rc4] non-critical faulres report

Ok, PGI 15.10 w/ -m32 failed in the same way as the earlier versions. -Paul On Tue, Jul 12, 2016 at 11:10 AM, Paul Hargrove wrote: > I have a lead on a 15.10 installation with -m32 support. > I will report results later. > > -Paul > > > On Tue, Jul 12, 2016 at 10:29 AM, J

Re: [OMPI devel] Change compiler

Murali, I typically configure with CC=clang CXX=clang++ on the configure command line. Editing of the files generated by configure (such as the Makefile) is not advisable. -Paul On Mon, Jul 18, 2016 at 1:06 PM, Emani, Murali wrote: > Hi all, > > I would like to know if there is Clang suppor

Re: [OMPI devel] PGI built Open MPI vs GNU built slurm

Gilles, My initial thought is that libslurm probably does require linking libpthread, either for for linking pthread_* symbols, or for proper *operation* (such as thread-safe versions of functions which override weak definitions in libc). If so, then neither omitting "-pthread" nor telling pgcc n

Re: [OMPI devel] PGI built Open MPI vs GNU built slurm

g. > > since -lpthread is pulled anyway from libslurm.la (or it was already set > by OpenMPI), then yes, discarding -pthread should do the trick. > > > Cheers, > > > Gilles > > On 7/26/2016 10:11 AM, Paul Hargrove wrote: > > Gilles, > > My initial thought is

[OMPI devel] [2.0.1.rc1] runtime failure on MacOS 10.6

On a Mac OSX 10.6 system: $ mpirun -mca btl sm,self -np 2 examples/ring_c' dyld: lazy symbol binding failed: Symbol not found: _strnlen Referenced from: /Users/paul/OMPI/openmpi-2.0.1rc1-macos10.6-x86-m32/INST/lib/openmpi/mca_pmix_pmix112.so Expected in: flat namespace dyld: Symbol not found:

[OMPI devel] [2.0.1.rc1] Solaris MPIX failure

On Solaris 11.3 on x86-64: $ mpirun -mca btl sm,self,openib -np 2 -host pcp-d-3,pcp-d-4 examples/ring_c' [pcp-d-4:25075] PMIX ERROR: NOT-SUPPORTED in file /shared/OMPI/openmpi-2.0.1rc1-solaris11-x86-ib-gcc/openmpi-2.0.1rc1/opal/mca/pmix/pmix112/pmix/src/server/pmix_server_listener.c at line 529 [p

Re: [OMPI devel] [2.0.1.rc1] runtime failure on MacOS 10.6

Mac and had no problem. However, I’m at 10.11, and so > I’m wondering if the old 10.6 just doesn’t have strnlen on it? > > What compiler were you using? > > On Aug 22, 2016, at 9:14 PM, r...@open-mpi.org wrote: > > Huh - I’ll take a look. Thanks! > > On Aug 22, 2016, at 9:11 P

[OMPI devel] [2.0.1.rc1] dlopen_test crashes with xlc and studio compilers

As with 2.0.0 I am still seeing "dlopen_test" crashing on two types of system: Linux/X86-64 with Oracle Studio Compilers and -m32 Linux/PPC with XLC In the Studio compilers case, the problem is only when using -m32, and ONLY with versions prior to 12.5 (no longer in beta, FWIW). So, this may be w

Re: [OMPI devel] [2.0.1.rc1] dlopen_test crashes with xlc and studio compilers

7;s correct: are you saying that 12.5 (GA/not beta) *does* handle > the dlopen test with -m32 properly? > > If so, it sounds like we should amend README to say that we support 12.5 > and nothing earlier (given that 12.5 is pretty old in itself). > > > > > > On Aug 23, 201

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

..@open-mpi.org wrote: > > Thanks Gilles! > > On Aug 23, 2016, at 3:42 AM, Gilles Gouaillardet < > gilles.gouaillar...@gmail.com> wrote: > > Thanks Paul, > > at first glance, something is going wrong in the sec module under solaris. > I will keep digging tomorrow &g

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

Ralph, That will allow me to test much sooner. -Paul On Wed, Aug 24, 2016 at 10:41 AM, r...@open-mpi.org wrote: > When you do, that PR has already been committed, so you can just pull the > next nightly 2.x tarball and test from there > > On Aug 24, 2016, at 10:39 AM, Paul Har

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

-Paul On Wed, Aug 24, 2016 at 10:44 AM, Paul Hargrove wrote: > Ralph, > > That will allow me to test much sooner. > > -Paul > > On Wed, Aug 24, 2016 at 10:41 AM, r...@open-mpi.org > wrote: > >> When you do, that PR has already been committed, so you can just pu

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

e was a runtime error, not a build error. > > > Cheers, > > > Gilles > > On 8/25/2016 12:00 PM, Paul Hargrove wrote: > > Giles, > > I have successfully built openmpi-v2.0.0-227-g917d293 (tonight's nightly > tarball) on Solaris 11.3 with both the Gnu and Stud

[OMPI devel] [2.0.1rc1] minor nits in README

A run of "spell README" produces (after manual filtering) the following misspelled words: appliation applicaions availble compatibile libeveny Memopy paramater relavant specfic It appears that us middleware authors don't know how to write "applications" ;-) README says: - Open MPI's run-time

[OMPI devel] [2.0.1rc1] ppc64 atomics (still) broken w/ xlc-12.1

I didn't get to test 2.0.1rc1 with xlc-12.1 until just now because I need a CRYPTOCard for access (== not fully automated like my other tests). It appears that the problem I reported in 2.0.0rc2 and thought to be as fixed by pr1140 was never /fu

[OMPI devel] [2.0.1rc1] type warnings from clang

Building w/ clang-3.4.2 on Linux/x86-64: /scratch/phargrov/OMPI/openmpi-2.0.1rc1-linux-x86_64-clang/openmpi-2.0.1rc1/opal/mca/btl/openib/btl_openib_component.c:2158:21: warning: implicit conversion from enumeration type 'btl_openib_receive_queues_source_t' to different enumeration type 'mca_base_v

[OMPI devel] [2.0-latest] unreachable code

Oracle Studio 12.5 C compiler on a recent v2.0 nightly tarball points out the following unreachable code: "/shared/OMPI/openmpi-2.0-latest-solaris11-x86-ib-ss12u5/openmpi-v2.0.0-227-g917d293/opal/mca/base/mca_base_component_repository.c", line 265: warning: statement not reached "/shared/OMPI/open

Re: [OMPI devel] C89 support

On Mon, Aug 29, 2016 at 8:32 AM, C Bergström wrote: [...snip...] > Based on the latest response - it seems that we'll just fork OMPI and > maintain those patches on top. I'll advise our customers not to use > OMPI and document why. > > Thanks again > __

Re: [OMPI devel] C89 support

Responses inline, below. On Mon, Aug 29, 2016 at 8:42 PM, C Bergström wrote: > On Tue, Aug 30, 2016 at 5:49 AM, Paul Hargrove wrote: > > > > On Mon, Aug 29, 2016 at 8:32 AM, C Bergström > > wrote: > > [...snip...] > >> > >> Based on the latest

Re: [OMPI devel] C89 support

On Tue, Aug 30, 2016 at 7:06 AM, C Bergström wrote: > On Tue, Aug 30, 2016 at 9:20 PM, Jeff Squyres (jsquyres) > wrote: > > On Aug 29, 2016, at 11:42 PM, C Bergström > wrote: > >> > >> Paul - Is this your typical post? I can't tell if you're trying to be > >> rude or it's accidental. > > > > I

Re: [OMPI devel] C89 support

On Tue, Aug 30, 2016 at 7:06 AM, C Bergström wrote: > > > > > 3. More complete patches for fixing the issues. Specifically, the 3 > provided patches fix certain issues in some parts of the code base, but the > same issues occur in other places in the code base. As such, the provided > patches a

Re: [OMPI devel] C89 support

Nathan, Unless I have misunderstood both Chris and the Clang bug report, the problematic functions are in glibc. So, addition of the gnu_inline attribute would probably require either modifying system headers or interposing ahead of them. -Paul On Tue, Aug 30, 2016 at 8:30 AM, Nathan Hjelm wrot

Re: [OMPI devel] 2.0.1rc2 released

I will report my findings as they come in from my testers. However, NERSC is down for quarterly maintenance which means I am w/o Intel compilers today. I am proud to have been verb-ified, but could I get some clarification on which "Hargroved" items are fixed? I *am* expecting that the following

[OMPI devel] Off-topic re: supporting old systems

On Tue, Aug 30, 2016 at 10:49 AM, Paul Hargrove wrote: [...] > > I still have systems running Red Hat Linux 8 (that would be something like > Fedora "negative 3"). > I had to accept that Open MPI moved forward while I did not - I use Open > MPI 1.6.5 on that system.

Re: [OMPI devel] Off-topic re: supporting old systems

On Tue, Aug 30, 2016 at 1:42 PM, Jeff Squyres (jsquyres) wrote: > On Aug 30, 2016, at 4:22 PM, Paul Hargrove wrote: > > > > It seems that a stock Debian Wheezy system cannot even *download* Open > MPI any more: > > > > $ wget -nv --no-check-certificate http://www

[OMPI devel] pmix3x passing -Wall to *all* compilers.

On a recent nightly tarball of 'master' (but not v2.0) I am seeing "-Wall" among the options passed to the compiler without any configure test to ensure this options is safe. The root cause seems to be the following (final) line in opal/mca/pmix/pmix3x/pmix/src/Makefile.am: AM_CFLAGS = -Wall

[OMPI devel] FYI: soon to lose IA64 access

I don't recall the details of the last discussion over which CPU architectures would be dropped effective when. However, apparently IA64 support is still present in both 2.0.1rc2 and master I suspect that I am currently the only member of this community with the ability to test IA64. So, I thought

Re: [OMPI devel] FYI: soon to lose IA64 access

more it might *finally* be time to kill the asm. If someone wants to use > IA64 they can use the builtin atomic support. > > -Nathan > > > On Aug 30, 2016, at 4:42 PM, Paul Hargrove wrote: > > > > I don't recall the details of the last discussion over which CPU

[OMPI devel] pmix3x broken on Solaris/x86 (no flock)

Just tried to build last night's master tarball on Solaris-11.3 on x86-64 hardware (but keep in mind the default ABI is ILP32). I see the following fatal error "/shared/OMPI/openmpi-master-solaris11-x86-ib-ss12u5/openmpi-dev-4716-g99b2664/opal/mca/pmix/pmix3x/pmix/src/dstore/pmix_esh.c", line 305

Re: [OMPI devel] Off-topic re: supporting old systems

t; $ wget -nv --no-check-certificate https://www.open-mpi.org/softw > are/ompi/v2.0/downloads/openmpi-2.0.1rc2.tar.bz2 > <http://www.open-mpi.org/software/ompi/v2.0/downloads/openmpi-2.0.1rc2.tar.bz2> > > Cheers, > > Gilles > > On 8/31/2016 9:44 AM, Christopher Samue

[OMPI devel] [2.0.1rc2] CRITICAL error in README

I believe that both the addresses and subscription URLs for the mailing lists are out-of-date in the README as shown in red below. I don't know if the list addresses might be forwarding, but those subscription URLs are definitely 404. -Paul The best way to report bugs, send comments, or ask quest

Re: [OMPI devel] Off-topic re: supporting old systems

opped at Wheezy. -Paul On Tue, Aug 30, 2016 at 7:16 PM, Christopher Samuel wrote: > On 31/08/16 12:05, Paul Hargrove wrote: > > > As Giles mentions the http: redirects to https: before anything is > fetched. > > Replacing "-nv" in the wget command with "-v&q

Re: [OMPI devel] 2.0.1rc2 released

On Tue, Aug 30, 2016 at 1:38 PM, Jeff Squyres (jsquyres) wrote: > On Aug 30, 2016, at 4:06 PM, Paul Hargrove wrote: > > > > I will report my findings as they come in from my testers. > > However, NERSC is down for quarterly maintenance which means I am w/o > Intel compi

[OMPI devel] [2.0.1rc2] SIGBUS on Linux/SPARC

On an emulated UltraSPARC system running Linux (and using V9 ABI) I was able to build the RC, but get a SIGBUS when running ring_c. The problem is an unaligned 64-bit access, as shown by the gdb session below. I have not tried, but it *might* be possible to reproduce on PPC64 via "prctl --unaligne

Re: [OMPI devel] [2.0.1rc2] SIGBUS on Linux/SPARC

//patch-diff. > githubusercontent.com/raw/open-mpi/ompi-release/pull/1357.patch ? > > > Cheers, > > > Gilles > > On 9/1/2016 2:12 AM, Paul Hargrove wrote: > > On an emulated UltraSPARC system running Linux (and using V9 ABI) I was > able to build the RC, but get a

Re: [OMPI devel] openmpi-2.0.0 - problems with ppc64, PGI and atomics

FWIW I have not seen problems when testing the 2.0.1rc2 w/ PGI versions 12.10, 13.9, 14.3 or 15.9. I am going to test 2.0.2.rc3 ASAP and try to get PGI 16.4 coverage added in -Paul On Thu, Sep 1, 2016 at 12:48 PM, Jeff Squyres (jsquyres) wrote: > Please send all the information on the build su

Re: [OMPI devel] 2.0.1rc3 posted

On Thu, Sep 1, 2016 at 1:47 PM, Jeff Squyres (jsquyres) wrote: > - Fix a Solaris alignment issue > If you mean the SIGBUS I reported that was Linux on SPARC h/w -Paul -- Paul H. Hargrove phhargr...@lbl.gov Computer Languages & Systems Software (CLaSS) Group Computer

Re: [OMPI devel] 2.0.1rc3 posted

ypo, and you should either read > > - Fix a SPARC alignment issue > > or > > - Fix an alignment issue on alignment sensitive processors such as SPARC > > > the patch i submitted to fix the issue you reported is definitely included > in 2.0.1rc3 > > > Cheers, > &

Re: [OMPI devel] openmpi-2.0.0 - problems with ppc64, PGI and atomics

> > > On Sep 1, 2016, at 8:25 PM, Paul Hargrove wrote: > > > > FWIW I have not seen problems when testing the 2.0.1rc2 w/ PGI versions > 12.10, 13.9, 14.3 or 15.9. > > > > I am going to test 2.0.2.rc3 ASAP and try to get PGI 16.4 coverage added > in > &

[OMPI devel] [2.0.1rc3] OpenBSD 6.0 patcher failure

The OpenBSD 6.0 release was announced slightly under 12 hours before Jeff announced the Open MPI 2.0.1rc3 tarball. So, I just *had* to try them out together. First, let me say that I have no expectation that the following issue be fixed for 2.0.1, but hopefully before 2.2. It appears that abort()

Re: [OMPI devel] 2.0.1rc3 posted

I can confirm that 2.0.1rc2+patch *did* run correctly on Linux/SPARC. I am running 2.0.1rc3 now, for completeness. -Paul On Fri, Sep 2, 2016 at 3:24 AM, Jeff Squyres (jsquyres) wrote: > > On Sep 1, 2016, at 8:42 PM, Gilles Gouaillardet > wrote: > > > > Paul, > > > > > > I guess this was a typo

Re: [OMPI devel] 2.0.1rc3 posted

All of my testing on 2.0.1rc3 is complete except for SPARC. The alignment issue on SPARC *has* been tested via 2.0.1rc2 + patch (so there is very low probability that 2.0.1rc3 would fail). At this point I am aware of only two platforms that fail that we didn't already know about: + OpenBSD-6.0 dis

Re: [OMPI devel] OMPI devel] RFC: Reenabling the TCP BTL over local interfaces (when specifically requested)

On Wed, Sep 21, 2016 at 9:36 AM, Gilles Gouaillardet < gilles.gouaillar...@gmail.com> wrote: > > if i want to exclude ib0, i might want to > mpirun --mca btl_tcp_if_exclude ib0 ... > > to me, this is an honest mistake, but with your proposal, i would be > screwed when > running on more than one no

[OMPI devel] master broken on (at least) OpenBSD-6

When trying to test PR2107 on OpenBSD-6 I was blocked by the following error, which is also present in 'master'. ../../../ompi/opal/util/if.c: In function 'opal_ifisloopback': ../../../ompi/opal/util/if.c:710: error: 'IFF_LOOPBACK' undeclared (first use in this function) ../../../ompi/opal/util/if

Re: [OMPI devel] heads up about OMPI/master

On Thu, Dec 1, 2016 at 4:25 PM, Gilles Gouaillardet wrote: [...] > git checkout master > > git merge --ff-only topic/misc_fixes > > git push origin master > [...] Gilles, You characterized the merge commit has having "close to zero added value" to you - but in this instance it would have saved

[OMPI devel] [2.0.2rc1] Fortran link failure with PGI fortran on MacOSX

I have Mac OS X 10.10 (Yosemite) and 10.12 (Sierra) systems with PGI compilers installed. I have configured the 2.0.2rc1 tarball with --prefix=[...] --enable-debug CC=cc CXX=c++ Where cc and c++ are Clang from Apple Xcode 7.1 (Build 7B91b) and 8.2 (Build 8C38). Meanwhile Open MPI's configure

[OMPI devel] [2.0.2rc1] Build failure w/ PGI compilers on Mac OS X

I have Mac OS X 10.10 (Yosemite) and 10.12 (Sierra) systems with PGI compilers installed. I have configured the 2.0.2rc1 tarball with --prefix=[...] --enable-debug CC=pgcc CXX=pgc++ FC=pgfortran I see a build failure in the libevent code: PGC-F-0249-#error -- "No way to define ev_uint64_t

Re: [OMPI devel] Open MPI v2.0.2rc1 is up

Fix a problem with MPI_IREDUCE when the same buffer is supplied for the > send and recv buffer arguments. Thanks to Valentin Petrov for reporting. > - Fix a problem with atomic operations on PowerPC. Thanks to Paul > Hargrove for reporting. > > -- > Jeff Squyres > jsquy

Re: [OMPI devel] [2.0.2rc1] runtime error w/ PGI usempif08 on OpenPOWER

Since the message below has still not appeared in the archive after more then 15hrs, I am resending w/o the attachment. -Paul On Thu, Dec 15, 2016 at 10:23 PM, Paul Hargrove wrote: > On a little-endian Power8 I have the free edition of PGI16.10 for > OpenPOWER. > I am configuring the

[OMPI devel] Errors with CXX=pgc++ (but CXX=pgCC OK)

With the 1.10.r5c1 tarball on linux/x86-64 and various versions of the PGI compilers I have configured with --prefix=[...] --enable-debug CC=pgcc CXX=pgc++ FC=pgfortran I see the following with version 14.3 of the PGI compilers: /bin/bash ../../../libtool --tag=CXX --mode=link pgc++ -g -ve

Re: [OMPI devel] Open MPI v2.0.2rc1 is up

t the config.log attached? > > Thanks, > > Howard > > > 2016-12-16 12:17 GMT-07:00 Howard Pritchard : > >> HI Paul, >> >> Thanks for the checking the rc out. And for noting the grammar >> mistake. >> >> Howard >> >> >>

[OMPI devel] [2.0.2rc2] FreeBSD-11 run failure

With the 2.0.2rc2 tarball on FreeBSD-11 (i386 or amd64) I am configuring with: --prefix=... CC=clang CXX=clang++ --disable-mpi-fortran I get a failure running ring_c: mpirun -mca btl sm,self -np 2 examples/ring_c' -- It

[OMPI devel] [2.0.2rc2] opal_fifo hang w/ --enable-osx-builtin-atomics

On Macs running Yosemite (OS X 10.10 w/ Xcode 7.1) and El Capitan (OS X 10.11 w/ Xcode 8.1) I have configured with CC=cc CXX=c++ FC=/sw/bin/gfortran --prefix=... --enable-osx-builtin-atomics Upon running "make check", the test "opal_fifo" hangs on both systems. Without the --enable-osx-builtin

[OMPI devel] [2.0.2rc3] build failure ppc64/-m32 and bultin-atomics

I have a standard Linux/ppc64 system with gcc-4.8.3 I have configured the 2.0.2rc3 tarball with --prefix=... --enable-builtin-atomics \ CFLAGS=-m32 --with-wrapper-cflags=-m32 \ CXXFLAGS=-m32 --with-wrapper-cxxflags=-m32 \ FCFLAGS=-m32 --with-wrapper-fcflags=-m32 --disable-mpi-fortran (Yes, I know

Re: [OMPI devel] Reminder: assign as well as request review

Ralph, It looks like GitHub *might* have rolled out the solution to your problem just this week: https://github.com/blog/2306-filter-pull-request-reviews-and-review-requests This appears to include an "Awaiting review from you" filter. Not quite a dashboard or notification, but at least a way to

[OMPI devel] [2.0.2rc4] "make install" failure on NetBSD/i386 (libtool?)

I had no problem with 2.0.2rc3 on NetBSD, but with 2.0.2rc4 I am seeing a "make install" failure (below). This is seen on an x86 (32-bit) platform, but not x86_64. I cannot say for certain that this is an Open MPI regression, since there *have* been s/w updates on this system since I last tested.

Re: [OMPI devel] Reminder: assign as well as request review

I am so often the guy complaining about what it busted. So, it feels nice to have contributed something *positive* on this list. -Paul On Fri, Jan 27, 2017 at 5:42 PM, r...@open-mpi.org wrote: > Thanks Paul - that does indeed help! > > On Jan 27, 2017, at 12:26 PM, Paul Hargro

Re: [OMPI devel] [2.0.2rc4] "make install" failure on NetBSD/i386 (libtool?)

Howard > > > > 2017-01-27 15:12 GMT-07:00 Paul Hargrove : > >> I had no problem with 2.0.2rc3 on NetBSD, but with 2.0.2rc4 I am seeing a >> "make install" failure (below). >> This is seen on an x86 (32-bit) platform, but not x86_64. >> I cannot say

Re: [OMPI devel] OMPI v1.10.6rc1 ready for test

Sorry for the delayed response. I have completed my normal RC testing and have nothing to report. -Paul On Mon, Jan 30, 2017 at 1:03 PM, r...@open-mpi.org wrote: > Usual place: https://www.open-mpi.org/software/ompi/v1.10/ > > Scheduled release: Fri Feb 3rd > > 1.10.6 > -- > - Fix bug in ti

[OMPI devel] [2.1.0rc2] ring_c SEGV on OpenBSD/i386

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 *** ---

[OMPI devel] [2.1.0rc2] PMIX build failures

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

[OMPI devel] [2.1.0rc2] PMIX failure running ring_c on NetBSD

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

Re: [OMPI devel] [2.1.0rc2] ring_c SEGV on OpenBSD/i386

? 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: > > RC2 tarball for 2.1.0 configured with only --prefix=... > and --enable-mca-no-build=patcher &

Re: [OMPI devel] [2.1.0rc2] ring_c SEGV on OpenBSD/i386

Both 2.1.0rc2 and 2.0.2 appear to crash about 1 run in every 5. This probabilistic nature is why I did not notice it in 2.0x. -Paul On Mon, Mar 6, 2017 at 7:58 PM, Paul Hargrove wrote: > I am traveling all this week and so don't know when I can take a look, but > will try. > -P

[OMPI devel] [2.1.0rc2] stupid run failure on Mac OS X Sierra

The following is fairly annoying (though I understand the problem is real): $ [full-path-to]/mpirun -mca btl sm,self -np 2 examples/ring_c PMIx has detected a temporary directory name that results in a path that is too long for the Unix domain socket: Temp dir: /var/folders/mg/q0_5yv791yz65cd

Re: [OMPI devel] [2.1.0rc2] stupid run failure on Mac OS X Sierra

is an entry 8 under OS-X FAQ which describes this problem. > > Adding max allowable len is a good idea. > > Howard > > Paul Hargrove schrieb am Di. 7. März 2017 um 08:04: > >> The following is fairly annoying (though I understand the problem is >> real): >> >

Re: [OMPI devel] [2.1.0rc2] stupid run failure on Mac OS X Sierra

the v2.1.x text. > > Thanks! > > > > On Mar 7, 2017, at 10:52 AM, Paul Hargrove wrote: > > > > I initially did a Google search on the error text and "Open MPI FAQ" > > Since the error message issued by 2.1.x no longer matches the text in > the FAQ entry

Re: [OMPI devel] Open MPI v2.1.0rc3 released

I am getting "make install" failures on NetBSD that are the same as seen once before: https://www.mail-archive.com/devel@lists.open-mpi.org/msg19906.html The fix that time was, I understand, to build release candidates on a different system. Note that due to problems fixed between rc2 and rc3,

Re: [OMPI devel] Open MPI 2.1.1rc1 is up

My testing was delayed since I was on vacation last week. I have run my normal range of tests and have no new issues to report. -Paul On Thu, Apr 27, 2017 at 12:14 PM, Howard Pritchard wrote: > Hi Open MPI developers, > > Open MPI 2.1.1rc1 is available for testing at the usual place: > > https:

Re: [OMPI devel] Open MPI 3.x branch naming

As a maintainer of non-MTT scripts that need to know the layout of the directories containing nighty and RC tarball, I also think that all the changes should be done soon (and all together, not spread over months). -Paul On Fri, May 5, 2017 at 2:16 PM, George Bosilca wrote: > If we rebranch fro

Re: [OMPI devel] Open MPI v2.0.3rc1 available for testing

On Fri, May 26, 2017 at 2:06 PM, Howard Pritchard wrote: > Hi Folks, > > Open MPI v2.0.3rc1 tarballs are available on the download site for testing: > [...] I am pleased to report that my testing found nothing new. -Paul -- Paul H. Hargrove phhargr...@lbl.gov Comput

[OMPI devel] [3.0.0rc1] ILP32 build failures

On every ILP32 build I try w/ gcc, I get the following. ../../../opal/.libs/libopen-pal.so: undefined reference to `__atomic_fetch_add_8' collect2: error: ld returned 1 exit status make[2]: *** [opal_wrapper] Error 1 This includes at least x86 and ppc32 (probably MIPS and ARM, but those are too s

[OMPI devel] [3.0.0rc1] XLC build error

With xlc-12.1 and 13.1 (big-endian PPC64, both LP64 and ILP32) there are numerous problems compiling with ompi_datatype_module.c (a prefix of which are shown below). -Paul libtool: compile: xlc -DHAVE_CONFIG_H -I. -I/home/hargrove/SCRATCH/OMPI/openmpi-3.0.0rc1-linux-ppc32-xlc-12.1/openmpi-3.0.0

Re: [OMPI devel] [3.0.0rc1] ILP32 build failures

omic_add_fetch (addr, delta, __ATOMIC_RELAXED); ^~ 1 error generated. On Mon, Jul 3, 2017 at 3:55 PM, Paul Hargrove wrote: > On every ILP32 build I try w/ gcc, I get the following. > > ../../../opal/.libs/libopen-p

[OMPI devel] [3.0.0rc1] ppc64/gcc-4.8.3 check failure (regression).

On a PPC64 host with gcc-4.8.3 I have configured with --prefix=[...] --enable-debug \ CFLAGS=-m64 --with-wrapper-cflags=-m64 \ CXXFLAGS=-m64 --with-wrapper-cxxflags=-m64 \ FCFLAGS=-m64 --with-wrapper-fcflags=-m64 I see "make check" report a failure from opal_fifo. Previous testing of Open MPI 2.

Re: [OMPI devel] [3.0.0rc1] ppc64/gcc-4.8.3 check failure (regression).

On a PPC64LE w/ gcc-7.1.0 I see opal_fifo hang instead of failing. -Paul On Mon, Jul 3, 2017 at 4:39 PM, Paul Hargrove wrote: > On a PPC64 host with gcc-4.8.3 I have configured with > > --prefix=[...] --enable-debug \ > CFLAGS=-m64 --with-wrapper-cflags=-m64 \ > CXXFLAGS=-m64

[OMPI devel] [3.0.0rc1] PMIX ERROR: UNPACK-INADEQUATE-SPACE

On (at least) two different hosts (both Linux, one x86-64 and one ppc64el) I am seeing a failure to launch ring_c with errors like those shown below. -Paul $ mpirun -mca btl sm,self -np 2 examples/ring_c [pcp-d-1:02255] PMIX ERROR: UNPACK-INADEQUATE-SPACE in file /home/phargrov/OMPI/openmpi-3.0.0

Re: [OMPI devel] [3.0.0rc1] PMIX ERROR: UNPACK-INADEQUATE-SPACE

l On Tue, Jul 4, 2017 at 9:46 AM, Artem Polyakov wrote: > Hello, Paul. > How OMPI was configured ? Were you by chance using external PMIx? > > пн, 3 июля 2017 г. в 18:43, Paul Hargrove : > >> >> On (at least) two different hosts (both Linux, one x86-64 and one >> pp

[OMPI devel] [3.0.0rc2] spurious xlc configure failures

With xlc-12.1 I am seeing spurious failures of configure tests due to multiple definitions of OPAL_ASM_SYNC_HAVE_64BIT: "conftest.c", line 211.9: 1506-236 (W) Macro name OPAL_ASM_SYNC_HAVE_64BIT has been redefined. "conftest.c", line 211.9: 1506-358 (I) "OPAL_ASM_SYNC_HAVE_64BIT" is defined on lin

[OMPI devel] [3.0.0rc2] yoinks, indeed

I have an x86 Linux system where configuring Open MPI 3.0.0rc2 yields: configure: WARNING: lib fabric requires both libnl v1 and libnl v3 -- yoinks! configure: WARNING: This is a configuration that is known to cause run-time crashes configure: error: Cannot continue I am happy to disable libfabri

[OMPI devel] [3.0.0rc2] pmix2x/libz link failure on NetBSD7

I am seeing the following on NetBSD-7.2/amd64: /bin/sh ../../../libtool --tag=CC--mode=link gcc -std=gnu99 -g -finline-functions -fno-strict-aliasing -mcx16 -pthread-o opal_wrapper opal_wrapper.o ../../../opal/libopen-pal.la -lrt -lexecinfo -lm -lutil libtool: link: gcc -std=gnu99 -g -fi

[OMPI devel] [3.0.0rc2] FreeBSD: divide-by-zero in hwloc

On FreeBSD-11/amd64: $ mpirun -mca btl vader,self -np 2 examples/ring_c [freebsd-amd64:25312] *** Process received signal *** [freebsd-amd64:25312] Signal: Floating point exception (8) [freebsd-amd64:25312] Signal code: Integer divide-by-zero (2) [freebsd-amd64:25312] Failing at address: 0x800c138

Re: [OMPI devel] v3.0.0 blocker issues

#3993 in particular has "xlc" in the description, but appears to be caused by bogus .m4. -Paul On Tue, Aug 1, 2017 at 3:07 PM, Barrett, Brian via devel < devel@lists.open-mpi.org> wrote: > Here’s the full list: https://github.com/open-mpi/ > ompi/issues?q=is%3Aissue%20is%3Aopen%20label%3A%22Targ

Re: [OMPI devel] Open MPI v2.1.2rc1 available

I have not yet had a chance to run this RC through all it paces. However, I can say that I have successfully built and run this RC on a system with Apple's latest public Betas of Mac OS High Sierra and Xcode 9. -Paul On Thu, Aug 10, 2017 at 11:47 AM, Howard Pritchard wrote: > Hi Folks, > > > O

[OMPI devel] [2.1.2rc2] CMA build failure on Linux/SPARC64

Both the v9 and v8+ ABIs on a Linux/SPARC64 system are failing "make all" with the error below. -Paul make[2]: Entering directory '/home/phargrov/OMPI/openmpi-2.1.2rc2-linux-sparcv9/BLD/opal/mca/btl/sm' CC mca_btl_sm_la-btl_sm.lo In file included from /home/phargrov/OMPI/openmpi-2.1.2rc2-

Re: [OMPI devel] [2.1.2rc2] CMA build failure on Linux/SPARC64

339 -Paul On Mon, Aug 21, 2017 at 6:56 PM, Paul Hargrove wrote: > Both the v9 and v8+ ABIs on a Linux/SPARC64 system are failing "make all" > with the error below. > > -Paul > > make[2]: Entering directory '/home/phargrov/OMPI/openmpi- > 2.1.2rc2-

Re: [OMPI devel] [2.1.2rc2] CMA build failure on Linux/SPARC64

t; 1) This is *NOT* present in 3.0.0rc2, thought I don't know what has > changed. > > > > 2) Here are the magic numbers: > > /usr/include/sparc64-linux-gnu/asm/unistd.h:#define > __NR_process_vm_readv > > 338 > > /usr/include/sparc64-linux-gnu/asm/un

Re: [OMPI devel] Open MPI 3.0.0rc4 available

I have nearly completed my normal suite of tests. Only slow emulated 32-bit ARM and MIPS remain. This time around I've dropped big-endian PPC (because Open MPI did). However, I've added Apple's public betas of Mac OSX High Sierra and Xcode 9. I have no new issues to report, and the ones I raised

[OMPI devel] [2.1.2rc3] libevent SEGV on FreeBSD/amd64

I am testing the 2.1.2rc3 tarball on FreeBSD-11.1, configured with --prefix=[...] --enable-debug CC=clang CXX=clang++ --disable-mpi-fortran --with-hwloc=/usr/local The CC/CXX setting are to use the system default compilers (rather than gcc/g++ in /usr/local/bin). The --with-hwloc is to avoid is

<    1   2   3   4   5   6   7   8   9   10   >