make-w32
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (no subject)


From: Eli Zaretskii
Subject: Re: (no subject)
Date: Tue, 26 Jun 2001 16:26:29 +0300 (IDT)

On Mon, 25 Jun 2001, Jason D. York wrote:

> I tried using the DJGPP port today, but it seems that it will not work with
> the compiler I am using.
> 
> Even with the DJGPP port, the compiler would not see more than 126
> characters of the command line.

Probably because the compiler is not a DJGPP program.

Does the compiler support the response file method of passing long
commands?  Judging by this:

> For now, I can get around the problem by using a series of
> echo commands and appending to a temporary file.

it does.  If so, using Bash as the shell for Make should solve this.

> Or, if it were possible to simply write the contents of a variable
> to a file as a make command, that would work too.

That's what the DJGPP port of Bash will do automatically.  To make
this work, first download and install the ported Bash (from the same
place where you got the DJGPP port of Make), and install it somewhere
along your PATH.  Then add this one line to your Makefile:

 SHELL = /bin/sh

Finally, you will have to force Make to invoke your compiler via Bash
(normally, it will avoid that as much as it can).  One way of doing
that is to include the name of the compiler in single quotes, like
'this'.

If this somehow doesn't work, either, you could at least ease your
pain by using a DJGPP port of `echo' (it's included in the port of GNU
Sh-utils package).  It will let you write all the command-line
arguments to the temporary file in one go, since Make can pass long
command lines to that port of `echo'.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]