Mail Archives: djgpp/1999/08/06/16:03:29
Campbell, Rolf [SKY:1U32:EXCH] (cp1v45 AT americasm01 DOT nt DOT com) wrote:
> Eli Zaretskii wrote:
> > > *) where can i get a list of the currently known bugs
> > > of djgpp?
> >
> > There are none ;-).
> >
> > Seriously, though: go to http://www.delorie.com/djgpp/bugs/ and see for
[...]
> Is that list only for bugs in the code changed to port gcc to DOS? Or
> is it for any bug that shows up in the DJGPP package regardless of origin?
It's even a bit more restrictive than that (at least it's meant to
be): The DJGPP Bug Tracker is for bugs *in* DJGPP (i.e. the C library
and tools), only. That's why there's a field to give the version
number of DJGPP, but none for your version of, say gcc or RHIDE. Bugs
in DJGPP ports of GNU programs, or any of the other packages (Allegro,
GRX, RHIDE etc.) should be mailed to their respective maintainers or
authors.
As a rule of thumb: if a patch to djdev*.zip can't fix the bug, the
report doesn't belong into the DJGPP Bug Tracker.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -