Date:	Tue, 25 Feb 1997 09:28:55 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Nikita Proskourine <nproskou AT goucher DOT edu>
cc:	djgpp AT delorie DOT com
Subject:	Re: using old libraries with new DJGPP
In-Reply-To:	<3311B70C.34D7@goucher.edu>
Message-ID:	<Pine.SUN.3.91.970225092307.6546F-100000@is>
MIME-Version:	1.0

On Mon, 24 Feb 1997, Nikita Proskourine wrote:

> Is there a way to use DJGPP libs developed for older versions of DJGPP
> (1.x) with new DJGPP without getting these 'could not read symbols:
> virtual memory exhausted' error. I heard that was a known bug, but is
> there a way to get around it without recompiling the source in 2.x?

The ``memory exhausted'' bug has nothing to do with v1.x as opposed to v2
issue.  The real reason for that is that ld from ported Binutils 2.6 and
2.7 don't support object files in AOUT format in libraries.  Please read
section 8.18 of the DJGPP FAQ list for more about this (no need to rely on
rumors here, since it's documented). 

> Another annoying thing: I thought that -l bug was fixed in ld (I am
> using ld to bypass libc.a. But when I provide -lpatch, it says that file
> -lpatch is not found and doesn't even look for libpatch.a.

I think the -lname conversion to libname.a is a feature of gcc, ld 
doesn't know anything about it.

> I also
> provide my own stub and do a few other weird things to get access to
> things like Windows GUI)

You should really study the ld docs if you need to put it to some 
advanced use such as the above.

- Raw text -