X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	DJGPP AT Delorie DOT com
Date:	Sat, 14 May 2011 10:19:41 +0300
From:	Eli Zaretskii <eliz AT gnu DOT org>
Subject:	Re: DJGPP V1.12 Link error ~\libxt.a: could not read symbols: Memory Exhausted
In-reply-to:	<e55250653cdd2365c9cfef07acf27ede@wacontrols.com>
X-012-Sender:	halo1 AT inter DOT net DOT il
To:	DJGPP AT Delorie DOT com
Message-id:	<83liy9g35e.fsf@gnu.org>
References:	<e55250653cdd2365c9cfef07acf27ede AT wacontrols DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Fri, 13 May 2011 15:41:09 -0500
> From: "John Wright" <john AT wacontrols DOT com>
> 
> The error in the subject line is what I'm getting.

Can you try invoking the link command from the command prompt?  Does
it fail with the same error message?  If it does, then recursion is
not the issue here.

In any case, since the linker is the one that complains, the problem
is not with the DOS memory, but with the extended memory used in
protected mode.  So I doubt the problem is with recursive invocations
anyway.

> I get the same error with the other demo clients. I have go32 "topline" enabled, but I have got to capture or redirect the output to a file. It compiles very fast now that I have disk cache and ramdisk configured. I could use a few tips on the best methods to capture and interpret what go32 is doing during the compile process. How do you step through or freeze "topline"?

What information you want to "freeze" there?

One "primitive" way is to press Ctrl-S to stop and Ctrl-Q to continue.

> Do I reply back to ALL or DJGPP AT delorie DOT com only? 

The latter.  Assuming you are subscribed to the mailing list (or read
the newsgroup), that will work just fine.

- Raw text -