From:	"John S. Fine" <johnfine AT erols DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: problems with nasm & rhide
Date:	Mon, 04 Jan 1999 20:29:01 -0500
Lines:	22
Message-ID:	<36916ADD.E41@erols.com>
References:	<36911B84 DOT C7BE8336 AT t-online DOT de>
Mime-Version:	1.0
X-Trace:	srUllK0NvGNXCs4VTHcMtZHDtYZWSUyTNsCB6rIg2P4=
X-Complaints-To:	abuse AT rcn DOT com
NNTP-Posting-Date:	5 Jan 1999 01:30:05 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

Tobias Kästner wrote:

> When I try to compile an *.asm (NASM) file from the Rhide-Env NASM
> reports me, that it is out of memory.

  The standard NASM.EXE version 0.97 was compiled with a 16-bit C
compiler, plus it has memory leak bugs.  These facts make it very
prone to running out of memory.

  The best solution is to get the NASM.EXE from the NASMEXE.ZIP
on my web page.  It was compiled with DJGPP.  It is a prerelease
of version 0.98 with most memory leaks and some other bugs fixed
and several enhancements.

  You could download the sources for NASM version 0.97.  They
contain a makefile to recompile with DJGPP.  You would still
have memory leaks, but in 32-bit mode you usually won't
notice them.  I think using the prerelease 0.98 is a much
better idea, but take your pick.
-- 
http://www.erols.com/johnfine/
http://www.geocities.com/SiliconValley/Peaks/8600/

- Raw text -