From: "A. Sinan Unur" Newsgroups: comp.os.msdos.djgpp Subject: Re: DJGPP gcc crashes when compiling under Windows 98 Date: 15 Nov 2001 20:45:03 GMT Organization: Cornell University Lines: 23 Sender: asu1 AT cornell DOT invalid (on 52.syracuse-02rh16rt.ny.dial-access.att.net) Message-ID: References: <9003-Thu15Nov2001212352+0200-eliz AT is DOT elta DOT co DOT il> NNTP-Posting-Host: 52.syracuse-02rh16rt.ny.dial-access.att.net X-Trace: news01.cit.cornell.edu 1005857103 13413 12.89.11.52 (15 Nov 2001 20:45:03 GMT) X-Complaints-To: usenet AT news01 DOT cit DOT cornell DOT edu NNTP-Posting-Date: 15 Nov 2001 20:45:03 GMT User-Agent: Xnews/4.06.22 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > Eli Zaretskii: >> That might or might not be relevant, but it's hardly a good idea. >> Why don't you use the DJGPP port of Bash instead of Cygwin's? peter karlsson wrote in news:slrn9v86as DOT cg DOT petekarl AT perkele DOT perkele: > I didn't know such a beast existed... Besides, I prefer to run > Cygwin's since it's a Windows program. i find life is much easier if you keep the two separate. start a djgpp bash when you need to build using djgpp. this should not have any of the cygwin stuff in the path, for example, not cygwin's config.site, but djgpp's should be found by configure scripts if you are building packages using djgpp. also, as eli pointed out, you will have problems with passing long command lines to djgpp programs if you run them in cygwin bash. sinan. -- -------------------------------- A. Sinan Unur http://www.unur.com/