Message-Id: <199908011643.SAA01120@robby.dittmannsdorf.de>
From: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Organization: none provided
To: djgpp-workers AT delorie DOT com
Date: Sun, 1 Aug 1999 18:43:48 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Changes in Binutils 2.9.1
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990801121450 DOT 20304f-100000 AT is>
In-reply-to: <Pine.SUN.3.91.990801121833.20304n-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.01d)
Reply-To: djgpp-workers AT delorie DOT com

> Apropos Binutils, there's a problem with the stub that the build
> procedure uses: that stub is part of the distribution, so it's always
> out of date.  It would be better if the stub could be generated at
> build time from whatever DJGPP version that is installed.

This would also not solve the problem in general, since this implies,
that you need to rebuild the binutils every time you change the stub.

I think the safest is to use the feature of all binutils (since it is in
BFD) to add a line in DJGPP.ENV like

GO32STUB=%DJDIR%/bin/stubify.exe

and any program using the BFD will use the stub from stubify.exe
when it needs to create a new stub for an output file.

Robert

******************************************************
* email:   Robert Hoehne <robert DOT hoehne AT gmx DOT net>     *
* Post:    Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW:     http://www.tu-chemnitz.de/~sho/rho        *
******************************************************