Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

From: Manuel Prinz (debian_at_[hidden])
Date: 2007-08-17 08:57:24

Am Freitag, den 17.08.2007, 14:49 +0200 schrieb Adrian Knoth:
> On Fri, Aug 17, 2007 at 08:26:50AM -0400, Jeff Squyres wrote:
> > > Ok, --enable-progress-threads and --enable-mpi-threads cause the
> > > segfaults. If you compile without, everything works.
> >
> > > I'll now try if it's mpi-threads or the progress-threads, and also
> > > check
> > > the upcoming v1.2.4.
> > The --enable-progress-threads and --enable-mpi-threads configure
> > options result in broken-ness on the v1.2 branch; you should not use
> > them.
> That's why I wondered why Debian has enabled them.

We enabled it because it was requested (

> Dirk: Do you mind removing them from debian/rules, thus fixing the
> issue?

I personally think it's best to disable it for now then and document it
in README.Debian. We can enable it again as soon as it works correctly.

Jeff, do you know for which architectures it's (not) working? I haven't
experienced problems so far, or at least didn't notice them.

Best regards