Date: Wed, 18 Jun 1997 12:44:40 +0200 (METDST)
From: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
To: DJ Delorie <dj AT delorie DOT com>
Cc: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: Latest stub for binutils
In-Reply-To: <199706171240.IAA28784@delorie.com>
Message-Id: <Pine.HPP.3.95q.970618123306.28538B-100000@newton.mathematik.tu-chemnitz.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

On Tue, 17 Jun 1997, DJ Delorie wrote:

> of that.  The Right Thing is to handle whatever size it is, so that
> you don't break in the future.
I agree. I will see if it is possible to allow this in the binutils
in a reasonable way.

> Nope, tried it.  Not all tools work when you do this (I don't recall
> which).
Some libc functions (v2loadimage(), dosexec related functions,
stubedit) and after this of course any program have to be
relinked with the new libc functions which have to handle
external executables to run or load them (make, go32-v2, ...)

> That's what the spec says, but that's not what Reality says.  EXE
> headers have to be a whole number of 512 byte blocks.

With Reality you mean DJGPP? Or is this assumed also by
other programs and/or systems? In DJGPP we have at many
points the silently assumption of the 512 byte exe-header
in the stub which fail also if we would have sometimes
in the future a exe-header of 1024 bytes.

Robert