Date: Tue, 3 Aug 1999 10:34:29 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Changes in Binutils 2.9.1
In-Reply-To: <Pine.LNX.3.93.990802185053.8447K-100000@acp3bf>
Message-ID: <Pine.SUN.3.91.990803103346.1847C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 2 Aug 1999, Hans-Bernhard Broeker wrote:

> Or, for similar purposes, why not install the 'stub.h' generated as part
> of the DJLSR build process, into $(DJDIR)/include/sys/go32stub.h or
> similar?

This will also work, but adding a header for the sake of a single
package seems like too much of a hassle.

> For the short term, it might be seen as part of the duty of whoever makes
> binutils binary distribution packages for DJGPP to ensure that the latest
> stub.h is included, and used.

This is of course true, but it doesn't solve the problem.  Too many
people are trying to build Binutils for themselves lately, see
c.o.m.d., so hand-crafted solutions would not fit the bill.

> FSF patches for this part of binutils should
> probably be submitted by DJ himself, every time a new DJGPP release is
> made. 

I was trying to find a way that would automatically use the latest
stub, so that DJ and others could be spared this burden.