From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Apr 1 21:40:22 2004 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D4E416A4CE for ; Thu, 1 Apr 2004 21:40:22 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2747A43D2F for ; Thu, 1 Apr 2004 21:40:22 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i325eMbv061542 for ; Thu, 1 Apr 2004 21:40:22 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i325eLwZ061541; Thu, 1 Apr 2004 21:40:21 -0800 (PST) (envelope-from gnats) Date: Thu, 1 Apr 2004 21:40:21 -0800 (PST) Message-Id: <200404020540.i325eLwZ061541@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Pav Lucistnik Subject: Re: ports/64964: audio/faad broken on amd64 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pav Lucistnik List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Apr 2004 05:40:22 -0000 The following reply was made to PR ports/64964; it has been noted by GNATS. From: Pav Lucistnik To: Tim Robbins Cc: freebsd-gnats-submit@FreeBSD.org, tim@robbins.dropbear.id.au, sean@sfarc.net Subject: Re: ports/64964: audio/faad broken on amd64 Date: Fri, 02 Apr 2004 07:36:32 +0200 V p=E1, 02. 04. 2004 v 07:34, Tim Robbins p=ED=B9e: > > Is this a FreeBSD specific issue? Does the file plays, say, on > > gentoo-amd64 Linux? Can submitter provide a fix on this? Can maintainer > > provide a fix on this? Have you talked to authors about this? >=20 > I doubt that it's FreeBSD-specific, but I'm not desperate enough to insta= ll > Linux just to play MPEG-4 audio :-) I'll see if I can come up with a fix, > but for the moment it should just be marked BROKEN on amd64 - the failure > mode is such that's it's not obvious just by running the program that it > is broken. Okay I can mark it broken for amd64 (maybe all 64 bit archs?). Does maintainer agree? --=20 Pav Lucistnik In God we trust. All others must use the callback verifier.