From:	Eric Backus <ericb AT lsid DOT hp DOT com>
Subject:	Re: Too many files on gcc command line at link phase
To:	raney AT metacard DOT com (Scott Raney)
Date:	Wed, 18 Nov 92 10:12:35 PST
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Mailer:	Elm [revision: 66.25]

>   This is probably a simple question (we're DOS impaired), but how
> does one go about putting a large number of files (about 500
> characters) on the gcc command line for the link phase?
>   We're using the gnuish make (thanks for the suggestions!) but
> something stops working (error 2) if there are more than about 100
> characters on the gcc command line.  Running the link as a batch file
> doesn't work either so it seems to be a DOS limitation.
>   In the olden days (early 80s) link specifications were usually put
> into a separate file.  Is this still necessary?  How is it done?
>   Thanks in advance for any advice,
>     Scott

If you are using GNUish make, put this line in your makefile:

LONGARGS = gcc

The LONGARGS variable is a list of programs that understand the GNUish
environment variable convention of passing long command lines.  All
go32 programs do, as of 1.08 (or was it 1.07?).  If you are making a
library or removing lots of files, you may want to set LONGARGS to
something like:

LONGARGS = gcc:ar:rm

The "old" way of putting link specifications into a separate file will
still work, assuming you have a convenient way of creating the
separate file.  But that is not necessary given the above method.
--
				Eric Backus
				ericb AT lsid DOT hp DOT com
				(206) 335-2495

- Raw text -