Xref: news-dnh.mv.net comp.os.msdos.djgpp:1148
Path: news-dnh.mv.net!mv!news.sprintlink.net!news.texas.net!news.kei.com!newshost.marcam.com!news.mathworks.com!gatech!howland.reston.ans.net!xlink.net!nntp.gmd.de!news.rwth-aachen.de!tabaqui!softbrek
From: softbrek AT tabaqui DOT informatik DOT rwth-aachen DOT de (Hans-Bernhard Broeker)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Weirdest compile error...
Date: 25 Jul 1995 15:45:39 GMT
Organization: RWTH -Aachen / Rechnerbetrieb Informatik
Lines: 23
References: <DBw302 DOT Lvy AT freenet DOT carleton DOT ca> <3uij5i$9as AT mserv1 DOT dl DOT ac DOT uk> <DBzqv6 DOT MwH AT freenet DOT carleton DOT ca>
Nntp-Posting-Host: tabaqui.informatik.rwth-aachen.de
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire) writes:


>I. Badcoe (mbbad AT s-crim1 DOT dl DOT ac DOT uk) writes:

>> You don't have to ctrl-break, you can pass gcc flags to tell it to stop after
>> any compile phase.

>Yeah, I heard about that... didn't know before. I'm that guy with the
>missing docs who posts here just about every day. :-)

Just as a quick tip: get rid of "2r1" and the like in GO32, and add this
flag to your gcc-command-line in case of error: 

	gcc -c foo.c ...... -save-temps

If given this flag, gcc will keep all its 
temporary files, under the names foo.i (CPP'ed), foo.s (cc1'ed), foo.o
(as'ed). Looking at these can be *very* helpful (to the experienced) to
find strange reasons for strange behaviours of gcc.

Hans-Bernhard