Date: Sun, 4 Feb 2001 09:02:41 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Dan Lewis <dan AT thelewishouse DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Prevent gcc from invoking stubify and using djgpp.djl?
In-Reply-To: <3A7CB78C.883EA594@thelewishouse.com>
Message-ID: <Pine.SUN.3.91.1010204085904.20547K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 3 Feb 2001, Dan Lewis wrote:

> Is there any way to:
> 
> 1) Prevent gcc from invoking stubify after it runs ld?
> 
> 2) Prevent gcc from giving ld DJ's linker command script? Although
> puttong "-Wl,-Tlink.cmd" on the gcc command line passes "-Tlink.cmd" to
> ld, gcc also gives ld DJ's script name, as in "-Tdjgpp.djl".

Both of these are determined by the `specs' file (which comes with the 
GCC distribution).  You can edit `specs' to remove those, if you 
understand the cryptic syntax of that file.

However, the Right Thing to do is simply invoke the linker directly, not 
via GCC.  Then you have full control on what does the linker do, and 
stibify won't be run, since it's GCC that runs it, not the linker.

Btw, why do you need these changes?