From: kagel AT quasar DOT bloomberg DOT com Date: Fri, 16 Aug 1996 11:42:29 -0400 Message-Id: <9608161542.AA05935@quasar.bloomberg.com > To: ichapman AT nortel DOT ca Cc: djgpp AT delorie DOT com In-Reply-To: <32121E83.7603@nortel.ca> (message from Ian Chapman on Wed, 14 Aug 1996 14:44:19 -0400) Subject: Re: gcc /lfile Reply-To: kagel AT dg1 DOT bloomberg DOT com From: Ian Chapman Date: Wed, 14 Aug 1996 14:44:19 -0400 I've moved all the djgpp files over and unzipped them. I've compiled and got a pile of warnings and a .o file for both c and c++ modules. Right now the warnings are not a worry as they are mostly due to lack of proto definitions. I'm a bit naughty in pre ansi c. What I've failed to find is how to get a listing from the compiler. In MIX power c I just commanded pc myfile /lfile /etc to get a .exe .mix and file.lst. The file.lst was great for looking at where the compiler failed to make sense of what I asked. What switch should I use to get a listing from the gcc compiler? You cannot get this kind of mixed listing from DJGPP. However, several programmer's editors can read the error messages and put you at the code line in another window. Emacs comes to mind, you can compile from within emacs and it will parse the errors and place you in the module with the error at the referenced line number. -- Art S. Kagel, kagel AT quasar DOT bloomberg DOT com A proverb is no proverb to you 'till life has illustrated it. -- John Keats