Message-ID: <199808011034400610.0020B228@pogwizd.tcs.uni.wroc.pl>
In-Reply-To: <901937504.4336@wren.supernews.com>
References: <6lglca$g50 AT ds2 DOT acs DOT ucalgary DOT ca>
 <901937504 DOT 4336 AT wren DOT supernews DOT com>
Date: Sat, 01 Aug 1998 10:34:40 +0200
From: "Pawel Kowalski" <pk AT tcs DOT uni DOT wroc DOT pl>
To: mattcorby AT exotrope DOT net, djgpp AT delorie DOT com
Subject: Re: RHIDE command-line length limit?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
Precedence: bulk

>On 8 Jun 1998 12:27:54 GMT, slapierr AT acs2 DOT acs DOT ucalgary DOT ca (Soleil Lapierre) wrote: 
>>Hi. Sorry if this has been covered, but I tried DejaNews and looked in 
>>all the documentation that seemed appropriate.
>>
>>A while back I was working on a C++ project using RHIDE and DJGPP and 
>>NASM. This project had lots of source files - over a dozen if I recall 
>>correctly. (I'm using DOS 7, BTW)
>>
>>Anyway, after the project grew to a certain number of files, linking 
>>would fail under RHIDE. By playing around with the number of optimization 
>>flags I had turned on, I discovered that the problem was that the command 
>>line was getting chopped off. So I made a makefile. Shelling out and 
>>running make worked fine, no matter how long the command line it generated.
>>
>>My question is this: Is there a way around this command line length 
>>limitation in RHIDE? It's a hassle to shell out every time I want to 
>>rebuild. 
>>
>>BTW, my compliments to the authors. RHIDE, DJGPP and NASM are 
>>excellent tools and I appreciate having them around.
>>
>>--
>>/* Soleil "Ra" Lapierre         http://www.cuug.ab.ca/~lapierrs/
>> *
>> * Birdie num-nums.
>> */

Maybe you have too old version of gcc? Type gcc -v. You need 2.8.1 version
to be able to pass command lines longer than 127 characters.

Pawel Kowalski