From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_05,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e1c373b49361c889
X-Google-Attributes: gid103376,public
From: Simon Wright <simon@pogner.demon.co.uk>
Subject: Re: gcc Arg List Too Long
Date: 1998/11/22
Message-ID: <x7v90h33b33.fsf@pogner.demon.co.uk>#1/1
X-Deja-AN: 414523668
X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98
References: <36536784.8FAE0B2@hiwaay.net> <36541A6A.730C9F28@gecm.com>
X-Complaints-To: abuse@demon.net
X-Trace: news.demon.co.uk 911754847 nnrp-04:12537 NO-IDENT
 pogner.demon.co.uk:158.152.70.98
Organization: At Home
Newsgroups: comp.lang.ada
Date: 1998-11-22T00:00:00+00:00
List-Id: <comp.lang.ada>

Pete Norton <pete.norton@gecm.com> writes:

> Anthony E. Glover wrote:
> 
> > When trying to build my executable, I get an error from gcc
> > during the link phase that says my argument list is too long.
> > Is there anyway to get around this without building archives?
> > Does anyone have a step-by-step explanation of how to build
> > and use archives in the gnat process?
> 
>  Do you use gnatmake for your builds ?  We have some 2500 object files, and
> growing, and build without any problem.

I think this depends on the OS? no trouble, I think, on Solaris or
Linux, but others (HP????) have problems ..

If I remember right, an upcoming release of GNAT will handle this
problem for you.