X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed; reply-type=original
Message-id: <6A08E58E7F1A4C4FA9C24400792CAACA@dev.null>
From: Gisle Vanem <gvanem AT broadpark DOT no>
To: djgpp AT delorie DOT com
References: <b5073a3e-7c76-4fb4-ad99-48e5c6929380 AT googlegroups DOT com>
 <87bo61sadv DOT fsf AT uwakimon DOT sk DOT tsukuba DOT ac DOT jp>
 <33cb891e-c2bc-4298-aef8-f327936e3862 AT googlegroups DOT com>
 <83ppuh11tt DOT fsf AT gnu DOT org>
 <4c889912-3e72-4732-8b3a-6a0092275cda AT googlegroups DOT com>
Subject: Re: strange problem with compiling ffmpeg 2.0 - libavcodec.a was not
 created
Date: Thu, 18 Jul 2013 13:11:14 +0200
X-Priority: 3
X-MSMail-priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Reply-To: djgpp AT delorie DOT com

"RayeR" <glaux AT centrum DOT cz> wrote:

> touch .version
> rm -f libavcodec/libavcodec.a
> ar rc libavcodec/libavcodec.a libavcodec/012v.o libavcodec/4xm.o ...
> 
> except the last line is 14379 chars long, maybe it's excessive for stupid MS 
> cmd.exe. But even if I run djgpp bash and then make it fails too. How to overcome 
> this problem?

You could use a response-file. Like:

libavcodec/libavcodec.a: $(OBJECTS)
  echo $(OBJECTS) > ar.tmp
  ar rc $@ @ar.tmp
  rm -f ar.tmp

Not sure if there's a limit then. I have had to use this trick
even with MingW building huge libs.

--gv