To: Eli Zaretskii Cc: Andris Pavenis , "Gurunandan R. Bhat" , Alexey Yakovlev , djgpp-workers AT delorie DOT com, fortran AT gnu DOT org Subject: Re: Inconsistencies between g77 v0.5.23 and v0.5.19 References: From: Dave Love Date: 13 Jul 1998 19:34:02 +0100 In-Reply-To: Eli Zaretskii's message of "Mon, 13 Jul 1998 11:02:29 +0300 (IDT)" Message-ID: Lines: 37 Precedence: bulk >>>>> "Eli" == Eli Zaretskii writes: Eli> If the reason is that older non-ANSI Unix libraries don't Eli> support "b" in a destructive way, then just test for ANSI Eli> (__STDC__) or Posix, and if one of those is supported, always Eli> use "b". This should solve the problem for DJGPP, as well for Eli> any other standard-complying environment. I'm not sure that's wise. I'd rather special-case DJGPP and similar systems. I don't see the problem with that from DJGPP's point of view. Eli> Or did I miss something? SunOS (or some other BSD-ish system(s)), I think, at least in some circumstances. I think there are comments about that somewhwre in the g77 configuration stuff. >> I don't think so. The behaviour for cygwin32, at least, depends >> on how you mount the file system, not on the library >> intrinsically. Eli> True, but AFAIK using "b" won't hurt, regardless of how the file Eli> system is mounted. It would if a configure test running a program indicated it wasn't needed but it really was when you come to use a different filesystem. Eli> The DJGPP port of Bash is perfectly capable of running GNU Eli> configure scripts natively, even on plain DOS. I have been Eli> doing that for almost two years now (although never for g77), Eli> with no problems at all. I'm quite surprised, but I'm glad if it works so well. I certainly failed with the only autoconfed (non-GNU) program I can remember trying under DJGPP. I'd expect various things to break because of filenames, if nothing else.