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: Sun, 20 Apr 1997 16:10:26 GMT
Organization: Into Beyond
Lines: 28
Message-ID: <335c0c99.2878832@news.playstation.co.uk>
References: <335815c1.4298411@news.playstation.co.uk> <3358B3EC.120EBF4C@ulthwe.foobar.co.uk>
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 Sat, 19 Apr 1997 13:00:44 +0100, Dave Smethurst
<djs@ulthwe.foobar.co.uk> did quoth at me:

>SOURCE	=	source.cpp
>OBJ	=	source.o

>Anyway ... you can set any variable really. But there are some which
>Make usually
>likes to reserve.... can't list all of them.

That doesn't solve the problem - they are macros rather than
environmental variables aren't they?

It is when the macros are expanded that problems occur.

Source = blah1.c blah2.c ... blah256.c

-> gcc blah1.c ... blah256.c

-> Command line > input limit

What is need is something like gcc @file where file contains the
command line. (like in Watcom).


* 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"