www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1998/07/14/06:16:07

Date: Tue, 14 Jul 1998 13:15:41 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Alexey Yakovlev <jack AT catalysis DOT nsk DOT su>
cc: Dave Love <d DOT love AT dl DOT ac DOT uk>, djgpp-workers AT delorie DOT com, fortran AT gnu DOT org
Subject: Re: Inconsistencies between g77 v0.5.23 and v0.5.19
In-Reply-To: <35AB115F.8778570F@catalysis.nsk.su>
Message-ID: <Pine.SUN.3.91.980714130856.7653A-100000@is>
MIME-Version: 1.0

On Tue, 14 Jul 1998, Alexey Yakovlev wrote:

>   A bug report and workaround are here:
>   http://www.delorie.com/djgpp/bugs/show.cgi?000143

There's also a patched libc available from the net:

  ftp://www-leedr.arme.cornell.edu/pub/djgpp-patches/
  http://www.cartsys.com/eldredge/djgpp-patches.html

I believe you can download each patched function individually (as a 
compiled .o object file) from these sites, as well as get the entire 
libc.a with all the patches.  A README file available from these places 
should explain more.

> I'm sure that many people wouldn't
> want to download libc sources just to recompile one function. Especially
> this concerns Fortran-under-DOS programmers. Many of them even never
> heard of a `patch' utility. They certainly will wait until corrected
> library appears (or switch to another compiler/platform).

That is why I think putting a patched source of the function into the 
distribution is a lesser evil in these cases.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019