Here's a trivial patch that seems to fix it:
--- autogen.sh (revision 25674)
+++ autogen.sh (working copy)
@@ -698,7 +698,9 @@
rm -f configure.patched
echo " ++ Modifying configure for Sun Studio Fortran compilers"
+ if test -f "config/modify-configure-for-sun-fortran.pl"; then
Unless someone sees an issue, I can add it.
On Dec 20, 2011, at 4:30 PM, Jeff Squyres wrote:
> Yeah, we've known about this one and mostly ignored it.
> It occurs when autogen.sh is in a non-root directory and tries to run that script in a place where it doesn't exist (it does exist in the root directory). We hadn't previously bothered to fix it because a) it's in autogen and users won't see it, b) we've revamped autogen on the trunk such that this doesn't happen anyway, and c) it's a non-fatal error (and reflects correct behavior anyway -- we don't need that script run anywhere except the root).
> I'll add it to the list, but I don't know if it'll actually get fixed.
> On Dec 20, 2011, at 6:22 PM, Paul H. Hargrove wrote:
>> While trying to resolve the gmake-vs-bmake problem I ran autogen.sh and saw:
>> /home/phargrov/OMPI/openmpi-1.5.5rc1/openmpi-1.5.5rc1/autogen.sh: line 701: config/modify-configure-for-sun-fortran.pl: No such file or directory
>> I suspect this just requires an addition to EXTRA_DIST in config/Makefile.am
>> Paul H. Hargrove PHHargrove_at_[hidden]
>> Future Technologies Group
>> HPC Research Department Tel: +1-510-495-2352
>> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>> devel mailing list
> Jeff Squyres
> For corporate legal information go to:
> devel mailing list