To: Alexey Yakovlev Cc: Eli Zaretskii , Andris Pavenis , djgpp-workers AT delorie DOT com, fortran AT gnu DOT org Subject: Re: Inconsistencies between g77 v0.5.23 and v0.5.19 References: <35A9B2D3 DOT 63A0D300 AT catalysis DOT nsk DOT su> From: Dave Love Date: 13 Jul 1998 19:54:11 +0100 In-Reply-To: Alexey Yakovlev's message of "Mon, 13 Jul 1998 13:10:11 +0600" Message-ID: Lines: 25 Precedence: bulk >>>>> "AY" == Alexey Yakovlev writes: AY> Changes to f/runtime always included undefining NON_ANSI_RW_MODES AY> and specifying some other flags like -DWANT_LEAD_0, -DPad_UDread AY> -DALWAYS_FLUSH, etc. Is there some particular reason to define ALWAYS_FLUSH for DJGPP? I don't know why it should be any different than for Unix. AY> configur.bat in gcc-2.8.1 is some relic from previous versions. AY> For DJGPP is simply calls 'sh djconfig.sh'. Not in my copy of gcc-2.8.1 or egcs. AY> 3. a new tmpfile() should be included in libg2c built for AY> DJGPP. It is a quick and dirty way but it should work. I'm not sure that's something I'd want to do. Is there something about it at delorie.com or elsewhere that we could reference in the problems list? It might be helpful to send changes for filenames etc. to the gcc and egcs bug lists. They certainly haven't been made in the current egcs sources (about to branch for a new release), which presumably means they aren't in gcc either.