Jeff,
I ran into some kind of link error, I think, with PGI 10.3 and OpenMPI
1.4.2 last year. I am building a new cluster and we have PGI 11.4
now. I am consulting my notes and patches from 1.4.2 to inspect 1.4.3
to see if the problems I had have been fixed. I found the .m4 files I
pat
With all the outputs from Paul and Sam, I think we'll be good.
...hmmm. Wait. I see that our 1.4.x configure *is* patched to have the extra
".". Here's the lines from configure in 1.4.3 and 1.4.4rc2:
# Portland Group C++ compiler
Below is a sampling of "pgCC -V" outputs in response to Jeff's question.
The complete output looks like:
$ pgCC -V
pgCC 11.1-0 64-bit target on x86-64 Linux -tp nehalem
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2011, STMicroelectronics, Inc. All Rights R
Jeff,
Is this guaranteed to work for all versions of the PGI compiler?
I.e., does "pgCC -V" always return something in the form of (digit)+
\. ?
I don't know, but I think so. See your Nov 2009 discussion of this
bug and Ralf Wildenhues' libtool.m4 patches at http://www.open-mpi.org/commu
Here is the 'pgCC -V' output from versions that I have access to.
$ pgCC -V
pgCC 7.1-6 64-bit target on x86-64 Linux -tp gh-64
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2007, STMicroelectronics, Inc. All Rights Reserved.
$ pgCC -V
pgCC 9.0-3 64-bit ta
(adding libtool-patches@gnu.org)
Is this guaranteed to work for all versions of the PGI compiler? I.e., does
"pgCC -V" always return something in the form of (digit)+\. ?
On May 17, 2011, at 8:52 PM, Larry Baker wrote:
> This bug applies to OpenMPI 1.4.x and 1.5.x.
>
> The libtool.m4 in conf
