From owner-freebsd-current@FreeBSD.ORG Wed Mar 3 07:49:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 519FA16A4CE; Wed, 3 Mar 2004 07:49:26 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0639D43D31; Wed, 3 Mar 2004 07:49:26 -0800 (PST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: from dibbler.crodrigues.org (h00609772adf0.ne.client2.attbi.com[66.31.45.197]) by comcast.net (sccrmhc11) with ESMTP id <2004030315492501100g2nfbe>; Wed, 3 Mar 2004 15:49:25 +0000 Received: from dibbler.crodrigues.org (localhost.crodrigues.org [127.0.0.1]) i23FnO29085833; Wed, 3 Mar 2004 10:49:28 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost) by dibbler.crodrigues.org (8.12.11/8.12.10/Submit) id i23FnOWb085832; Wed, 3 Mar 2004 10:49:24 -0500 (EST) (envelope-from rodrigc) Date: Wed, 3 Mar 2004 10:49:24 -0500 From: Craig Rodrigues To: Alfred Perlstein Message-ID: <20040303154924.GA85824@crodrigues.org> References: <20040303061144.GE56622@elvis.mu.org> <404592F5.1060206@freebsd.org> <20040303104657.GG56622@elvis.mu.org> <20040303105149.GH56622@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040303105149.GH56622@elvis.mu.org> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: fix for libpthread X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 15:49:26 -0000 On Wed, Mar 03, 2004 at 02:51:49AM -0800, Alfred Perlstein wrote: > I see somehow it got linked against BOTH libpthread and libc_r, > there has to be a way to prevent that sort of bogus linkage > from happening. :( Or at least make it work right when it > does happen... You either need to either: -> update the mplayer port and rebuild it -> or, send a PR to the mplayer port maintainer and tell them to fix the port to respect PTHREAD_LIBS in /usr/ports/Mk/bsd.port.mk It's a pain in the neck, but many ports need to be fixed so that they don't link libc_r and libpthread at the same time. -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org