X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=LZRYNQjIlLft4+UkTpkriMGnY0KD87jw6oAh7+KO/E0=;
        b=NSfmSF7j5hbg4QYekIzkQG+gMeoN0hDdmLfQKzkNDwlRusU4nefg40My84ofhwxKxJ
         TV7z8nHKlfqa+fCKGoRzQwtzHOx2OyK4PCkwORV9LcdtUk/nxSERBkiUgg8ip6kmvmMs
         Biz809hcVsuqCrcdQMDwpWahMX4LBMbDGnyMaBXBtHK79WWvIa1MQcsx1/3qjkUo8xW2
         Es9FGNtWUTvPx6jVvRUWadPEHG7Y0ZIpp/BrJ2m8gkZplQqZGYHhxjhEUztSQxHlOQK4
         qdECGLLDx3utHE6tf+RaAzdGpUb2AHhaSyRJNuhpGz/RwRJaSZDwPHo39Z1yk/n0McDf
         X2HA==
MIME-Version: 1.0
X-Received: by 10.66.252.234 with SMTP id zv10mr8181385pac.186.1374071738441;
 Wed, 17 Jul 2013 07:35:38 -0700 (PDT)
In-Reply-To: <33cb891e-c2bc-4298-aef8-f327936e3862@googlegroups.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>
Date: Wed, 17 Jul 2013 17:35:38 +0300
Message-ID: <CAA2C=vDoczba0gyD_yA=OPNM+1LufJkLxK7-PWsqF6tf90n51g@mail.gmail.com>
Subject: Re: strange problem with compiling ffmpeg 2.0 - libavcodec.a was not created
From: Ozkan Sezer <sezeroz AT gmail DOT com>
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset=ISO-8859-1
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

On Wed, Jul 17, 2013 at 5:10 PM, RayeR <glaux AT centrum DOT cz> wrote:
>> ar(1) is failing.  Find out what AR expands to and run it by hand; it
>> may give you a better message.
>
> How can I display what command really make executes? Bug in ar/binutils? I could try different version.

I guess the issue may be in the makefile you are using where AR
is defined to something, so the issue may be with the package's
configury system.

Running ranlib on the generated *.a file may fix the issue (or may not
if the issue is elsewhere.)