Date:	Mon, 1 Apr 1996 07:19:20 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	John Fortin <fortin44 AT eelab DOT newpaltz DOT edu>
Cc:	djgpp AT delorie DOT com
Subject:	Re: DPMI error when compile/link with graphic library
In-Reply-To:	<199603311742.MAA23430@eelab.newpaltz.edu>
Message-Id:	<Pine.SUN.3.91.960401070007.11946A-100000@is>
Mime-Version:	1.0

On Sun, 31 Mar 1996, John Fortin wrote:

> > > >gcc calc.c -lgr
> > > 
> > > DPMI: Not enough memory (0x400a0000 bytes).
> > > c:\verktyg\djgpp\lib/libgr.a: could not read symbols: Memory exhausted
> > > 
> > > What to do?
> > 
> > Invoke go32 without any arguments and post what it prints.
> > 
> > 
> 
> This is the same error you get with RSXWDK when compiled with the 
> ld.exe from v1.12 and above.  The ld.exe from 1.11 does not have the 
> problem. 

Not as far as I know.  The known problem of ld.exe doesn't print the 
``DPMI: Not enough memory'' message, just the ``Memory exhausted'' one.  
The only cases I know of that print the DPMI error message are VERY old 
versions of DJGPP.  Running go32 with no arguments should print the 
version (and the amount of memory available).

> This question has been asked before:  Why the difference and can't it 
> be fixed???

ld.exe from DJGPP 1.11 was from a different revision of GNU Binutils; all 
versions of DJGPP from 1.12 and on use Binutils 2.5.2.
The problems seems to be a genuine one of the GNU Binutils, not something 
specific to DOS, so it should be reported to GNU.  Anyway, I never saw 
anybody reporting the exact cause of it, so I don't think anybody knows 
what exactly to fix.  Do you?

- Raw text -