Paul's probably more than likely right. The nightly runs Oracle does
using MTT and tarballs do not do autogen.sh (which I believe is not
expected anyways, right). All other builds we do using autogen.* are
from an svn workspace.
--td
On 12/20/2011 8:21 PM, Paul H. Hargrove wrote:
Not too
:-)
We usually do a better job of ensuring files are properly included in the
tarball, though
On Dec 20, 2011, at 6:21 PM, Paul H. Hargrove wrote:
> Not too bizarre.
> This probably just means that nobody has ever run autogen.sh from a tarball
> on a system using Sun's FORTRAN compiler.
>
Not too bizarre.
This probably just means that nobody has ever run autogen.sh from a
tarball on a system using Sun's FORTRAN compiler.
-Paul
On 12/20/2011 5:01 PM, Ralph Castain wrote:
Bizarre - fixed it too, but no promise when that might appear in a release.
Thanks!
On Dec 20, 2011, at
Bizarre - fixed it too, but no promise when that might appear in a release.
Thanks!
On Dec 20, 2011, at 5:10 PM, Paul H. Hargrove wrote:
> You are welcome.
> NOTE: the same issue exists in 1.4.5rc1
>
> $ grep for-sun-fortran openmpi-1.4.5rc1/autogen.sh
>
You are welcome.
NOTE: the same issue exists in 1.4.5rc1
$ grep for-sun-fortran openmpi-1.4.5rc1/autogen.sh
config/modify-configure-for-sun-fortran.pl
$ tar tfj openmpi-1.4.5rc1.tar.bz2 | grep
modify-configure-for-sun-fortran.pl || echo NOPE
NOPE
-Paul
On 12/20/2011 3:55 PM, Ralph
