X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Thu, 18 Jul 2013 05:54:53 +0300 From: Eli Zaretskii Subject: Re: strange problem with compiling ffmpeg 2.0 - libavcodec.a was not created In-reply-to: <4c889912-3e72-4732-8b3a-6a0092275cda@googlegroups.com> X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp AT delorie DOT com Message-id: <83ehaw1ssi.fsf@gnu.org> References: <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> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Wed, 17 Jul 2013 15:31:16 -0700 (PDT) > From: RayeR > > There's nothing unusual > > 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? If your ar is a DJGPP program (as it should be), the cmd limitations should be irrelevant, because DJGPP passes arguments by a different method. That method has the default size limitation of 16KB, so if your environment is large, 14379 might be too long. You can work around this by splitting the ar command into 2, or by stubedit-ing your make.exe to give it a larger transfer buffer.