From owner-freebsd-ports Sat Feb 2 6:10: 6 2002 Delivered-To: freebsd-ports@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 499CA37B402 for ; Sat, 2 Feb 2002 06:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12EA3W24674; Sat, 2 Feb 2002 06:10:03 -0800 (PST) (envelope-from gnats) Date: Sat, 2 Feb 2002 06:10:03 -0800 (PST) Message-Id: <200202021410.g12EA3W24674@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Alexander Leidinger Subject: Re: ports/34552: lame don't compile Reply-To: Alexander Leidinger Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR ports/34552; it has been noted by GNATS. From: Alexander Leidinger To: floripa@organiKa.com.br Cc: freebsd-gnats-submit@FreeBSD.ORG, murray@FreeBSD.org Subject: Re: ports/34552: lame don't compile Date: Sat, 2 Feb 2002 14:02:31 +0100 (CET) On 2 Feb, Antonio Carlos Venancio Junior wrote: >>Fix: > I think is something releated to nasm because building with nasm-0.98 (old) goes ok, but with nasm-0.98.21 (current) give the releated errors. Yes, this is caused by a change in nasm. Those people of the LAME development team which looked into this issue said, it's because of a bug in nasm, not because of a bug in the nasm code in LAME. Some .rpm/.deb versions of nasm work, perhaps the maintainer of nasm (CCed) can have a look at it? Bye, Alexander. -- 0 and 1. Now what could be so hard about that? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message