From owner-freebsd-ports Mon Mar 25 16:20: 9 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 AF65137B417 for ; Mon, 25 Mar 2002 16:20:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2Q0K2a56161; Mon, 25 Mar 2002 16:20:02 -0800 (PST) (envelope-from gnats) Date: Mon, 25 Mar 2002 16:20:02 -0800 (PST) Message-Id: <200203260020.g2Q0K2a56161@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Giorgos Keramidas Subject: Re: ports/34797: xmame links with wrong libusb Reply-To: Giorgos Keramidas 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/34797; it has been noted by GNATS. From: Giorgos Keramidas To: Ken Stailey Cc: bug-followup@freebsd.org Subject: Re: ports/34797: xmame links with wrong libusb Date: Tue, 26 Mar 2002 02:10:26 +0200 Adding to audit trail: | | Date: Fri, 22 Mar 2002 13:20:49 +0100 | From: Stijn Hoop | To: kstailey@surfbest.net | Cc: johnjen@reynoldsnet.org | | Hmm. I really don't think this is an xmame problem. It sounds like the | libusb port shouldn't install a shared library of the same name if it isn't | binary compatible; any other port could run into the same problem. | | CC: maintainer of the libusb port. | | --Stijn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message