Path: chuka.playstation.co.uk!news
From: alex@teeth.demon.co.uk (Alex Amsel)
Newsgroups: scee.yaroze.programming.gnu_compiler
Subject: Re: gcc DOS line length limit
Date: Tue, 22 Apr 1997 12:19:30 GMT
Organization: Into Beyond
Lines: 26
Message-ID: <335eab5c.2579978@news.playstation.co.uk>
References: <335815c1.4298411@news.playstation.co.uk> <3358B3EC.120EBF4C@ulthwe.foobar.co.uk> <335c0c99.2878832@news.playstation.co.uk> <335B4DBF.46E6@interactive.sony.com> <335eb23e.5674319@news.playstation.co.uk> <335C8EDA.5972@interactive.sony.com>
Reply-To: alex@teeth.demon.co.uk
NNTP-Posting-Host: teeth.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Newsreader: Forte Agent .99g/32.335

On Tue, 22 Apr 1997 11:11:38 +0100, SCEE Developer Support
<dev_support@interactive.sony.com> did quoth at me:

>Can you tell me why you want over 160 characters of DOS command
>line? What operations of that character-length
>can be better done on command line than in a makefile?

When the makefile calls gcc (or any program) it passes across a series
of parameters. So it will actually effectively 'input'

gcc -o blather.c ......other.c

So if your effective command length reaches 160 chars you have the
same problem again.

And it is easy to reach that limit, especially if porting code around.


Just a pain really, not a /serious/ problem.

I'm sure the DOS implementation must have a way around this.


* Alex Amsel * Into Beyond Web Design & JAVA Programming *
* http://www.intobeyond.com  *  WWFC Utter Rubbish 1996-7*
MM - "Steve Corica is every bit as good as that Kinkladze"