X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Rugxulo Newsgroups: comp.os.msdos.djgpp Subject: Re: Bash bugs (was: djgpp/libreadline bug) Date: Wed, 7 Apr 2010 14:13:16 -0700 (PDT) Organization: http://groups.google.com Lines: 21 Message-ID: References: <013d25d6-f34d-4686-9c68-0de775d5bf59 AT t20g2000yqe DOT googlegroups DOT com> <81255c92-b71b-4d8b-871c-fe057d72ddb7 AT u22g2000yqf DOT googlegroups DOT com> <834ojz111c DOT fsf AT gnu DOT org> <9e95b163-ba8a-467d-870e-4f3437dd9a96 AT y17g2000yqd DOT googlegroups DOT com> <1433b3f4-9d44-455b-9465-e873fd2cb618 AT 33g2000yqj DOT googlegroups DOT com> <8d449cf5-3dce-48c8-b8e7-e535b037b4a6 AT 8g2000yqz DOT googlegroups DOT com> <83zl1oxzat DOT fsf AT gnu DOT org> <81hah9Fit3U1 AT mid DOT individual DOT net> <4BB4C8EC DOT 8050909 AT iki DOT fi> <83r5mywcqy DOT fsf AT gnu DOT org> <45780149-957b-4e1a-9c91-fc01b4f040e4 AT y17g2000yqd DOT googlegroups DOT com> <834ojox8qw DOT fsf AT gnu DOT org> NNTP-Posting-Host: 65.13.115.246 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1270674796 18589 127.0.0.1 (7 Apr 2010 21:13:16 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Wed, 7 Apr 2010 21:13:16 +0000 (UTC) Complaints-To: groups-abuse AT google DOT com Injection-Info: h27g2000yqm.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO User-Agent: G2/1.0 X-HTTP-UserAgent: Opera/9.80 (Windows NT 5.1; U; en) Presto/2.5.22 Version/10.51,gzip(gfe) Bytes: 2946 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hi, On Apr 6, 9:05=A0pm, Eli Zaretskii wrote: > > From: Rugxulo > > Date: Tue, 6 Apr 2010 13:42:13 -0700 (PDT) > > > I don't want DJGPP (support) to die, it's too dang useful. But even > > when all the tools work (G++, GNU Make, Bison, Flex, Perl, PCRE, > > SQLite, Lua), some developers still abandon it > > Usually, this happens because no one works with the upstream > developers on DJGPP support. =A0Most of them will happily keep DJGPP if > there's a DJGPP maintainer. =A0When there isn't one, they drop DJGPP as > an obsolete unsupported platform. People always make lots of excuses for not supporting DJGPP. But there's a big difference between, "I don't know how to get it to build on DJGPP" and "Don't care, won't integrate your changes, use your builds, or even try to use DOS-friendly tools." A lot of things that used to support DJGPP fine aren't supported anymore. It's not always an unlucky accident, that's all I'm saying.