Message-ID: <35A9B2D3.63A0D300@catalysis.nsk.su>
Date: Mon, 13 Jul 1998 13:10:11 +0600
From: Alexey Yakovlev <jack AT catalysis DOT nsk DOT su>
Organization: Inst. of Catalysis
MIME-Version: 1.0
To: Dave Love <d DOT love AT dl DOT ac DOT uk>
CC: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, Andris Pavenis <pavenis AT lanet DOT lv>,
        djgpp-workers AT delorie DOT com, fortran AT gnu DOT org
Subject: Re: Inconsistencies between g77 v0.5.23 and v0.5.19
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980712192223 DOT 27114O-100000 AT is> <rzqpvfb2aq8 DOT fsf AT djlvig DOT dl DOT ac DOT uk>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi. 
 The story of g77 under DJGPP v2 is as following. In 1995 I found on the
Net (http://users.hol.gr/~kkou) g77-0.5.18 compiled for DJGPP but it was
very unstable. When v0.5.19 appeared I downloaded sources and after some
work compiled it natively for DJGPP under Windows 95. After some testing
I uploaded it on ftp.delorie.com. After that I compiled and used for my
everyday work all subsequent g77 versions. They all were  compiled
natively under win95. For the v0.5.19 a modified configur.bat was used
but then I found that configure script is much more convenient. Changes
to f/runtime always included undefining NON_ANSI_RW_MODES and specifying
some other flags like -DWANT_LEAD_0, -DPad_UDread -DALWAYS_FLUSH, etc.
The NON_ANSI_RW_MODES case may be treated in configure.in exactly the
same way as for cygwin32 and this definitely won't break anything. It is
all what is really necessary for g77 to work under DJGPP. However to
link programs compiled with g77-0.5.23, according to Eli, a patched
version of libc's tmpfile() must be supplied. 

On 11 Jul 1998, Dave Love wrote:

> Does `port' mean that there are other changes to the source necessary
> that we (fortran) don't know about, or just mean the build on DJGPP?
 No. Just build.
> If other changes are needed, I expect we'd be happy to have them.  For
> instance, does the build now work with the normal configure under
> DJGPP bash or are (fixes to) the .bat files still needed?

  Build now works with configure and .bat is not needed.

> I don't understand why this is only now a problem.  I don't think that
> part of the configuration has changed since 0.5.19, but I've not used
> g77 seriously on DJGPP and never done a native build.  Can you say
> exactly what has changed between the releases to cuase this so that we
> can understand it?

 Nothing changed significantly. Before, all the changes made to
configuration were left unposted but they were (almost) all the same
from version to version. I understand that probably it is my fault
because I built g77-0.5.19 distributed as a part of DJGPP. Perhaps, it
is now time to make these changes included to standard g77 distribution.

 Thus, the conclusions (maybe obvious for somebody) are as following:
1. configur.bat is not needed any more (bash works just fine).
2. f/runtime/configure.in should be patched against NON_ANSI_RW_MODES.
3. a new tmpfile() should be included in libg2c built for DJGPP. It is a
quick and dirty way but it should work. 
 
Best regards.
Alexey Yakovlev.