Mail Archives: djgpp-workers/1998/07/14/08:07:59
Date sent: 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>
Copies to: 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
>
> 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.
>
Simply one idea:
Maybe it would be usefull to create specialized packages (larger
than normal ones included in DJGPP distribution) that would be
easier to use in such situations. For example for poeple that uses
Fortran only. In this situation we should put djdev201, bnu281b,
gcc281b, mak3761b, g770523b and maybe something else in
either single archive or several archives (simply to make them
smaller) that ALL should be unzippped. After that only thing user
should do is to set DJGPP environment variable and put
$DJDIR/bin directory on the path.
- Raw text -