If you didn't catch it, 1.4.1rc1 went out yesterday evening.
If all goes well (gulp!), we'll ship 1.4.1 "final" shortly...
On Dec 28, 2009, at 8:37 PM, Joshua Bernstein wrote:
> Thanks Ralph,
>
> I'll keep an eye out...
>
> -Josh
>
> Ralph Castain wrote:
> > Sometime Jan, would be my
Thanks Ralph,
I'll keep an eye out...
-Josh
Ralph Castain wrote:
Sometime Jan, would be my best guess...but I am not in charge of it, so don't
take that as any kind of commitment.
On Dec 28, 2009, at 5:59 PM, Joshua Bernstein wrote:
Ralph Castain wrote:
You definitely shouldn't
Sometime Jan, would be my best guess...but I am not in charge of it, so don't
take that as any kind of commitment.
On Dec 28, 2009, at 5:59 PM, Joshua Bernstein wrote:
>
>
> Ralph Castain wrote:
>> You definitely shouldn't ship that one - it may build, but it doesn't work.
>> We are looking
Ralph Castain wrote:
You definitely shouldn't ship that one - it may build, but it doesn't work. We
are looking at a bug in that code branch prior to releasing.
I have no plans to ship that one. Any idea when we'll see a 1.4.1 release?
-Josh
You definitely shouldn't ship that one - it may build, but it doesn't work. We
are looking at a bug in that code branch prior to releasing.
On Dec 28, 2009, at 3:54 PM, Joshua Bernstein wrote:
>
>
> Jeff Squyres wrote:
>> Sorry -- I neglected to update the list yesterday: I got the RM approva
Jeff Squyres wrote:
Sorry -- I neglected to update the list yesterday: I got the RM approval and
committed the fix to the v1.4 branch. So the PGI fix should be in last
night's 1.4 snapshot.
Could someone out in the wild give it a whirl and let me know if it works for
you? (it works for *me*)
Jeff,
Subject: Re: [OMPI users] Problem building OpenMPI with PGI compilers
From: Jeff Squyres
Date: Thu, 10 Dec 2009 10:20:32 -0500
To: Open MPI Users
...
Actually, I was wrong. You *can't* just take the SVN trunk's autogen.sh and
use it with a v1.4 tarball (for various uni
Sorry -- I neglected to update the list yesterday: I got the RM approval and
committed the fix to the v1.4 branch. So the PGI fix should be in last night's
1.4 snapshot.
Could someone out in the wild give it a whirl and let me know if it works for
you? (it works for *me*)
On Dec 10, 2009,
On Dec 10, 2009, at 4:02 PM, Joshua Bernstein wrote:
> > On Dec 9, 2009, at 4:36 PM, Jeff Squyres wrote:
> > Given that we haven't moved this patch to the v1.4 branch yet (i.e., it's
> > not
> > yet in a nightly v1.4 tarball), probably the easiest thing to do is to apply
> > the attached patch to
Jeff Squyres wrote:
On Dec 9, 2009, at 4:36 PM, Jeff Squyres wrote:
Given that we haven't moved this patch to the v1.4 branch yet (i.e., it's not
yet in a nightly v1.4 tarball), probably the easiest thing to do is to apply
the attached patch to a v1.4 tarball. I tried it with my PGI 10.0 insta
On Dec 9, 2009, at 4:36 PM, Jeff Squyres wrote:
> That's the commit message for r22273. Also see the commit message for r22274
> (https://svn.open-mpi.org/trac/ompi/changeset/22274).
>
> Meaning: the fix is now in the SVN trunk; it hasn't migrated over to the v1.4
> and v1.5 branches yet. It'
Hi All
As I stated on my original posting,
I haven't compiled OpenMPI since 1.3.2.
Just trying to be of help, based on previous,
and maybe too old, experiences.
The problem I referred to happened with PGI 8.0-4 and OpenMPI 1.3.
Most likely the issue is superseded already by the newer
OpenMPI con
Just to set the record straight: it's a Libtool problem with PGI version 10
(all PGI versions below 10 work fine).
This has been reported to the GNU Libtool folks and patches have already been
applied upstream. However, there hasn't been a new Libtool release yet with
these patches, so we have
Fascinating. I've not had any real problems building it from scratch
with PGI. We are using the PGI 9 compilers, though, for that.
gerry
Gus Correa wrote:
Hi David
Last I tried, OpenMPI 1.3.2, PGI (8.0-4) was problematic,
particularly for C and C++.
I eventually settled down with a hybrid gc
Hi David
Last I tried, OpenMPI 1.3.2, PGI (8.0-4) was problematic,
particularly for C and C++.
I eventually settled down with a hybrid gcc, g++, and pgf90
(for both OpenMPI F77 and F90 bindings).
Even this required a trick to avoid the "-pthread" flag
to be inserted among the pgf90 flags (where
That's the commit message for r22273. Also see the commit message for r22274
(https://svn.open-mpi.org/trac/ompi/changeset/22274).
Meaning: the fix is now in the SVN trunk; it hasn't migrated over to the v1.4
and v1.5 branches yet. It's an autogen.sh fix -- you should be able to
download auto
16 matches
Mail list logo
