Mail Archives: djgpp/2002/07/09/02:38:13
On Mon, 8 Jul 2002, buddy lott wrote:
> 1) Command lines that are too large. I gave tried the response file method
> for resolving this and it doesn't seem work for me. I have not tried the
> !proxy method but it seems to apply only to gnu related tools (which this is
> not) and I have not seen an example of how to use it. I finally settle on
> echoing the command to a batch file ($*temp.bat) and executing it which
> works on Windows 2000 but not on WinNT4.0. Is there a better way?
Please tell the details of the failures, and please show what you tried
to solve them. The issues are subtle but solutions can be found given
enough information.
!proxy won't worfk with anything but DJGPP programs, so don't try that
with Windows programs.
> 2) Having used the batch file fix mentioned in #1. I get into a problem with
> using '$*temp.bat' as the file name becuase it results in file names that
> are too long some times. I don't like it, but I can get around this by using
> the same small file name for all batch files (i.e. temp.bat). Is there a
> better way?
A better way is to create a separate directory for each temp file, and
then have the same file name for batch files in each directory. This has
the advantage of solving the potential file-name conflicts without
bumping into problems with long file names.
> 3) For all the $*temp.bat files that do work I get a "Program too big to fit
> in memory" error. The bat files run fine from the command in a WinNT dos
> prompt session, but I can not run then from the make file. I can seem to get
> past this one.
Please show an example of a rule from your Makefile that causes such an
error message. I suspect that somehow Make tries to run the batch file
directly, instead of invoking the shell to do that, but I cannot tell for
sure without seeing the command it tries to run.
- Raw text -