Xref: news2.mv.net comp.os.msdos.djgpp:5765
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: memory exhausted?!?!
Date: Tue, 09 Jul 1996 08:14:11 CDT
Organization: Rice University, Houston, Texas
Lines: 18
Message-ID: <31e25b23.sandmann@clio.rice.edu>
References: <31E1A0B2 DOT 3BEA AT owb DOT mindspring DOT com>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> When I attempt to link my object file and the library which is
> about 420k, I get "could not read symbols: memory exhausted."  Any fix I
> could apply or am I doing something hideously wrong?

There are a whole bunch of problems in the ld currently being used in 
DJGPP.  There is the problem mentioned above, plus the problem if a large
global/static array is declared.  There are also performance problems
due to fseek.  This may sound terrible, but I ended up pulling the linker out 
of V1.11 (which used binutils 2.4 instead of 2.5) and it seems to work fine 
in all these cases.  

Yes, someone needs to fix ld.  I don't know if binutils 2.6 fixes the problems
we see with 2.5 (or makes them worse...).  It may be a bug with ld assuming
memory is zeroed (but since V1.12 had some problems too, that's not all of it).
We could just build ld 2.4 with V2 and be done with it.

DJ is well aware of the problems, it's just a matter of finding the time
to work through it.