From: elf AT netcom DOT com (Marc Singer)
Message-Id: <199604242103.OAA09939@netcom4.netcom.com>
Subject: Re: Standard 32-bit libraries
To: UCKO AT vax1 DOT rockhurst DOT edu (Aaron Ucko)
Date: Wed, 24 Apr 1996 14:03:01 -0700 (PDT)
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu (DJGPP List Alias)
In-Reply-To: <01I3X2XKRRSY0060YC@VAX1.ROCKHURST.EDU> from "Aaron Ucko" at Apr 24, 96 11:48:29 am
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 965

> I'm not punning you this time...but don't you remember when V2 was being 
> planned one or two years ago, a discussion of whether or not DJGPP should
> simultaneously switch to ELF.  Unless I am mistaken, you expressed opposition
> and I made a lame pun about your not wanting an identifier collision.
> 
> >I've been looking at ELF format for other things and have grown to
> >appreciate the layout.  COFF is very difficult to identify and parse,
> >while ELF is designed to be revisioned.
> 
> Glad you've come around.  I guess the switch'll have to wait until V3,
> though. :-(  (Or maybe not.  In the Linux binutils there is a script to
> convert archives from a.out to ELF; perhaps it could be adapted for
> use with DJGPP.)

Harumph.  Guess that one fell off the far end of my memory a while ago.

The real issue is the DJGPP loader.  The compiler already has the
pieces, but the loader probably does not.  

V3?  What could be added to the current setup?