Date:	Wed, 16 Dec 1998 18:07:40 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Charles Krug <charles AT pentek DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Trying to isolate build errors.
In-Reply-To:	<3677C640.4455F78B@mail.pentek.com>
Message-ID:	<Pine.SUN.3.91.981216175328.25041A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Wed, 16 Dec 1998, Charles Krug wrote:

> make.exe:  *** [bsp_bifo.out] Error -1

This usually means that either Make couldn't find some file, or it failed 
to run the command in the rule that failed.  Please post the rule that 
failed together with its commands, and the command echoed by Make when it 
tried to execute it (use `redir' if you need to redirect Make's output).

Since the failure happened when you ``added a second source file'' (can't
say I really understand what that means, either), it could be that the
problem is releated to long command lines.  Seeing the command that Make
tried to issue would show whether this is indeed the problem. 

> Texas Instruments C compiler and assembly language tools for the TI
> tms320c6x DSP, 2.11, dos version.

These probably were built with something other than DJGPP, right?

If so, long command lines won't work, since there's no general method of 
passing them to DOS programs (DJGPP programs use the techniques described 
in section 16.4 of the DJGPP FAQ list).

Another possibility is that they compiled their tools with a compiler 
that emits protected-mode code which is incompatible with the 32-bit DPMI 
environment used by DJGPP.  If they supply real-mode versions of the 
compiler/linker/whatever, try them and see if it helps.

> I suspect that they don't correctly
> handle command lines longer than 127 characters when they made the port.

I'm not sure why do you expect long command lines to work at all.  They 
only work in DJGPP because DJGPP programs have private tricks to work 
around DOS limitations.  But these tricks won't work when you invoke 
non-DJGPP programs from the DJGPP port of Make.

If the TI tools can use respone files, change your Makefiles so that 
instead of invoking a long command directly, you write it to a file (with 
e.g. echo.exe which comes with DJGPP) and then invoke the compiler/linker 
on that response file.

> I don't suspect that the djgpp port of gmake is at fault.  I'm just trying
> to eliminate a variable, so TI doesn't turn around and say, "well, obviously
> your make is broken" when I seriously doubt that's the case.

I'm confused.  Didn't you say that you were using the DJGPP port of 
Make?  If not, how all this is relevant to DJGPP at all (the compiler is 
obviously not DJGPP, I understand)?

- Raw text -