Date:	Mon, 11 Oct 1993 10:51:43 -0400
From:	davis AT amy DOT tch DOT harvard DOT edu ("John E. Davis")
To:	ae1181t AT stnfor DOT ae DOT ge DOT com
Cc:	ahelm AT email DOT tuwien DOT ac DOT at, djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	gcc call too long (>128)
Reply-To:	davis AT pacific DOT mps DOT ohio-state DOT edu (John E. Davis)

>Use response files (put the .o filenames into a file) and use @filename
>on the link/compile line. This should also work with .c files.
>If you put all of your .o files in a subdir maybe  /dirname/*.o would
>also work.

Does anyone have a hacked up version of make that automatically generates a
response file without any modification to the makefile?  That is, interpret:

target:
	$(CC) ....lots of stuff here requiring response file....

as
target:
	$(CC) @target.rsp

where the file target.rsp is automatically generated by the make program.  It
would also be nice if files with .o extension were expanded to a .obj
extension.   I know much of this could be done with macros but I would like to
take a generic Unix Makefile and have the make program quietly but
intelligently `dosify' it.

--John

- Raw text -