Message-ID: <3291FC4E.1479@pobox.oleane.com>
Date: Tue, 19 Nov 1996 19:28:30 +0100
From: Francois Charton <deef AT pobox DOT oleane DOT com>
Organization: CCMSA
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: djgpp AT delorie DOT com
Subject: Re: ld2.4 vs ld2.5.2
References: <Pine DOT SUN DOT 3 DOT 91 DOT 961117101936 DOT 12547d-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Eli Zaretskii wrote:
> 
> I'm not sure what do you want me to say there.  The problem with ld is
> already discussed there.  Do we want to say that EMXAOUT is buggy? 

Well not exactly : the problem seems to be (I am told) with the AOUT 
format which EMXAOUT outputs. It links OK when alone, but not in an 
archive file. So this is not an EMXAOUT bug, and not a real ld bug (just 
a limitation).

In the FAQ, you recommend EMXAOUT as a way of porting Borland/MS ".lib" 
libraries to DJGPP, what I had in mind was just saying that the resulting 
object files could crash the linker when put in a library, so, you had 
better link them as something.o files.


> I think somebody said on the news group about a month ago
> that a fixed version is available; I'm not sure if COFF support was one
> of the new features. 

I tried using the last version (from Scitech software) of EMXAOUT, and 
the problem was still there.

As regards ways of overriding the problem (without solving the bug), one 
would be to develop a small tool (and maybe to include it in ar or 
ranlib) which converts AOUT files to COFF. 

Regards,
Francois