On Friday, Jul 11, 2003, at 18:58 Europe/Brussels,
wgscott@xxxxxxxxxxxxxxxxxx wrote:
This is an error I have gotten with either g77 3.1 or 3.3 if you
upgrade to the developer tools patch that installs gcc 3.3. The only
way I was able to get rid of this problem was to reinstall the
December 2002 edition of the developer tools. Merely switching back
to gcc 3.1 did not get rid of this problem. I tried reporting it
before but ...
A slightly longer way ... :
1) in autoconf2.5, add the line
PatchScript: sed -i -r 's|^(\ *)(end]\))|\1call\ exit\n\1\2|g'
lib/autoconf/fortran.m4
(and do a similar patch for extutils-f77 for a couple of perl-modules :
in F77.pm, add a line
print OUT " call exit\n";
right after the line :
print OUT " print *, 'Hello World'\n";
)
2) After rebuilding those 2, the configure stage in other builds should
proceed normally,
provided you add, if necessary, in a PatchScript to run autoconf (or
autoreconf (-f)) ,
and, if necessary, fix, before running autoconf, the .m4 files in the
builddir. Thus, eg,
PatchScript: <<
sed -i -r 's|^(\ *)end$|\1call\ exit\n\1end|g' *.m4 m4/R.m4
autoconf
<<
3) As to the make proper, the following line is safe to add in the
PatchScript, and will as far
as I know correct the problems in the sources :
egrep -r '^\ *(STOP|stop)$' *|grep '\.f:'|cut -f1 -d':'|xargs sed -i -r
's,^\ *(STOP|stop)$,&\ 999,g'
Best,
JF Mertens
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
|
