Bug#995599: libopenmpi3: segfault in mca_btl_vader.so on 32-bit arches

Thanks for the investigation and confirmation! -- Jeff Squyres jsquy...@cisco.com

Bug#995599: libopenmpi3: segfault in mca_btl_vader.so on 32-bit arches

I'm sorry, I just noticed that you replied 6 days ago, but I apparently wasn't notified by the Debian bug tracker. :-( Ok, so this is an MPI_Alltoall issue. Does it use MPI_IN_PLACE? On Wed, 06 Oct 2021 20:15:38 +0200 Drew Parsons wrote: > Source: openmpi > Followup-For: Bug #995599 > > Not

Bug#995599:

Can you provide a small reproducer of the issue?

Bug#947148: Open MPI and libltdl

I just replied on the upstream Open MPI issue (https://github.com/open-mpi/ompi/issues/7331#issuecomment-579337035): I'm not sure about that test: if you get a valid handle value back from lt_dlopen(), is the value from lt_dlerror() relevant? I.e., is the "handle" value you're getting back fro

Bug#896861: More notes on Open MPI / sometimes "-l" issues

On Sep 7, 2018, at 1:29 AM, Alastair McKinstry wrote: > >> I am using: >> >> Autoconf 2.69 >> Automake 1.15 (*** you are using 1.15.1 -- do we think that makes a >> difference?) >> Libtool 2.4.6 > > Something about Debian's libtool still implicated, then. Ouch -- that could get tricky to tra

Bug#896861: More notes on Open MPI / sometimes "-l" issues

On Sep 6, 2018, at 2:19 PM, Adrian Bunk wrote: > > With thanks to Santiago Vila we finally figured out how to reproduce it. > > From a failed build log: > I: NOTICE: Log filtering will replace 'build/openmpi-LjweZK/openmpi-3.0.1' > with '<>' > I: NOTICE: Log filtering will replace 'build/openmp

Bug#896861: More notes on Open MPI / sometimes "-l" issues

On Apr 27, 2018, at 2:02 PM, Alastair McKinstry wrote: > >> If we're not able to get the CI build product, has anyone been able to >> reproduce the error manually? > No one's caught it manually yet :-( Computers are hard. > Debian libtool has a bunch of patches applied > (https://sources.debi

Bug#896861: More notes on Open MPI / sometimes "-l" issues

On Apr 27, 2018, at 12:57 PM, Alastair McKinstry wrote: > > Before configure the following is run: > > (cd config && autom4te --language=m4sh opal_get_version.m4sh -o > opal_get_version.sh) > ./autogen.pl --force Ah -- you *are* running autogen and re-bootstrapping our tarballs

Bug#896861: More notes on Open MPI / sometimes "-l" issues

Thanks to Alastair for filing https://github.com/open-mpi/ompi/issues/5114 to inform us upstream of this issue. When this problem occurs, can you tell: 1. Is the errant "-l" being added by libtool (i.e., at "make" time)? 2. Or is the errant "-l" being added by configure (i.e., at "./configure" t

Bug#720419: [OMPI devel] Openmpi 1.6.5 is freezing under GNU/Linux ia64

On Sep 30, 2013, at 11:05 AM, Sylvestre Ledru wrote: > Here are the options list: > configure: running /bin/bash './configure' CFLAGS="-DNDEBUG -g -O2 > -Wformat -Werror=format-security -finline-functions -fno-strict-aliasing > -pthread" CPPFLAGS=" -I/usr//include -I/usr/include/infiniband > -

Bug#592326: [Pkg-openmpi-maintainers] Bug#592326: Failure of AZTEC test case run.

Adding pthread could fix something, but I'm a little dubious. It seems unlikely. You should probably contact the Aztec authors at this point. Sent from my PDA. No type good. On Sep 3, 2010, at 3:05 AM, Rachel Gordon wrote: > Dear Jeff, Ralf and Manuel > > There are some good news, > I a

Bug#592326: [Pkg-openmpi-maintainers] Bug#592326: Failure of AZTEC test case run.

If you're segv'ing in comm size, this usually means you are using the wrong mpi.h. Ensure you are using ompi's mpi.h so that you get the right values for all the MPI constants. Sent from my PDA. No type good. On Sep 2, 2010, at 7:35 AM, Rachel Gordon wrote: > Dear Manuel, > > Sorry, it d

Bug#531522: mpicc segfaults when called by fakeroot

nes in a single mpi job - see faq) and for debugging. I'll be back in range in several hours (boarding a floight right now). -jms Sent from my PDA. No type good. - Original Message - From: Manuel Prinz To: Steve M. Robbins Cc: Jeff Squyres (jsquyres); 531...@bugs.debian.org <