Date: Sun, 21 Dec 1997 09:36:31 -0800 (PST)
Message-Id: <199712211736.JAA29461@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: tessman AT remove-to-reply DOT interlog DOT com (Kent Tessman), djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: Simple Rhide stuff (help) anybody
Precedence: bulk

At 06:47  12/20/1997 GMT, Kent Tessman wrote:
>In article <349A7B91 DOT 125A AT nortel DOT ca>, Ian Chapman <ichapman AT nortel DOT ca> wrote:
>>DID YOU "LINK"!!! COMPILE THEN LINK or BUILD ALL to compile and link.  I
>>normally exit rhide and type the project name to run.  Stay away from
>>makefile till you get the hang of the basic stuff.  Make is used to
>>build or port a gob of code onto a new system.  Like Allegro onto a
>>xxxxx operating system.  When you run make you go to lunch, it's usuall
>>a massive batch type job.  Ian.
>
>I've always had to use make for my large-ish project, which takes about ten to 
>twelve C sources.  RHIDE's problem is that it seems to limit the length of a 
>command-line to DOS's--so long 'gcc -c ...' compile commands and longer 'gcc 
>-o ___.exe ...' link commands get trunctated, the result being that gcc can't 
>find 'x', where 'x' is some portion of a valid filename.
This is normally caused by old DJGPP versions trying to interact with new
ones. What version are your RHIDE, GCC, MAKE, etc.?

Nate Eldredge
eldredge AT ap DOT net