Mail Archives: djgpp/1997/03/26/18:25:13
> BTW, is there any ports of gcc2722 to djgpp?
Not yet. None of the changes affect djgpp at all, so the only reason
to port it is (1) principle, or (2) to add in other patches that
aren't quite "official" yet (in gcc or libc).
For example, I have two patches (Um, section naming and sdb symbols)
that the FSF recently accepted but didn't make it into 2.7.2.2. Since
they accepted them, I can use the 2.7.2.2 release as an opportunity to
rebuild gcc with those extra patches and the latest libc without
confusing people be re-releasing a previous version (2.7.2.1).
I don't know when I'll get around to actually building it, though. If
anyone feels strongly that they need it quickly, you have four
choices:
1. Sulk. If you do this, please do it privately.
2. Do it yourself. This is always an option, but remember that gcc is
so fundamentally central to djgpp, I'll probably have to build it
myself eventually anyway just to keep my build area sane.
3. Send me money. Nobody ever does this, but it's the best way to
affect my priorities :-) (*)
4. Wait patiently.
DJ
(*) Of course, you could send me money for no reason at all! This
goes for anyone else who you feel has contributed something to djgpp
that you appreciate. Portraits of presidents (or other gifts) make
excellent thank-you's for your favorite contributor.
- Raw text -