From: noname AT noname DOT org (Stuart Hall) Newsgroups: comp.os.msdos.djgpp Subject: Re: ECGS, DJGPP & GCC -- what's the difference Date: Wed, 09 Jun 1999 12:59:28 GMT Organization: Connix Internet Lines: 40 Message-ID: <375f64f8.3655464@news> References: <7jk854$3atp2$1 AT titan DOT xtra DOT co DOT nz> <375DFDD5 DOT 6095CC24 AT a DOT crl DOT com> NNTP-Posting-Host: m5.aetna.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Newsreader: Forte Agent 1.5/32.452 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Very interesting question. So why would I want to use ECGS and not GCC, or vice versa? Is one or the other more compliant with the ANSI C++ standard by any chance? On Wed, 09 Jun 1999 00:38:29 -0500, Weiqi Gao so kindly spent valuable time writing: >Steve Ball wrote: >> >> Can someone explain to me in simple terms what the difference between these >> three compilers are? DJGPP is based on GCC isn't it? And ECGS too? > >There are only two compilers: GCC and EGCS. DJGPP provides the stuff >that make GCC and EGCS possible in DOS. > >> Was the migration of GCC to DOS (producing DJGPP) a one-time thing or can I >> upgrade the GCC component of DJGPP to take advantage of the latest GCC >> features? > >Whoever does the porting has to do a lot of work. But that has already >been done. You can just download the gcc 2.8.x binaries replace the gcc >2.7.x stuff with the 2.8.x stuff. > >> Also, are ECGS and DJGPP "competing" DOS UNIX-style compilers? Does ECGS >> have a RHIDE equivalent? > >No. You can download the egcs 2.90.x binaries and drop it in to DJGPP. >Again the hard work has already been done for you. > >> Rather a few questions, I know, but I'd be keen to hear an explanation! > >When I said download binaries, I mean the binaries distributed in the >DJGPP archive. If you go out to the Cygwin site and download their >egcs, that's not going to work in DOS. ---- Stuart Hall Connecticut, USA * return address: f p r i n t f @ i n a m e . c o m *