From: "John S. Fine" Newsgroups: comp.os.msdos.djgpp Subject: Re: silly question (I read the FAQ first). Date: Tue, 23 Feb 1999 20:59:29 -0500 Lines: 26 Message-ID: <36D35D01.6F83@erols.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: j1pqRUE24A3YIMpuPbCDkmdO/fU+8Rk979SovBhyXHY= X-Complaints-To: abuse AT rcn DOT com NNTP-Posting-Date: 24 Feb 1999 02:00:47 GMT X-Mailer: Mozilla 3.01 (Win95; U) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Dave Bird wrote: > nasm -fcoff -lfred.l fred.asm > > Errors are reported, NO LISTING FILE "FRED.L" IS PRODUCED. Strange :-? > surely the listing is where you look to analyse and correct your errors > (unless I've misunderstood the commands, of course). NASM is a simple two pass assembler. It is very hard to write a program that goes forward reasonably after encountering severe errors in its input. NASM does not do this as well as commercial assemblers do. I expect some of your errors were severe enough that NASM couldn't even start its second pass, so it never started writing to the listing file. The error messages output by the assembler are where I look to analyse errors. I redirect those errors to a file and use a text editor (brief) that knows about .err files. Each time I press ^N it displays the next error from the .err file and moves my cursor to the source line of the error. (I know there are GNU etc. editors that do similar things, don't flame me for prefering an old commercial one instead). -- http://www.erols.com/johnfine/ http://www.geocities.com/SiliconValley/Peaks/8600/