From owner-freebsd-stable@FreeBSD.ORG Mon Nov 5 10:43:33 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBB8B16A421 for ; Mon, 5 Nov 2007 10:43:33 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 49E9413C4BE; Mon, 5 Nov 2007 10:43:33 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <472EF3D4.70507@FreeBSD.org> Date: Mon, 05 Nov 2007 11:43:32 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Norberto Meijome References: <20071105210626.49f84cc5@meijome.net> In-Reply-To: <20071105210626.49f84cc5@meijome.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable ML Subject: Re: Understanding libpthread.so.2 undef reference error.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2007 10:43:34 -0000 Norberto Meijome wrote: > Hi list, > I'm using 7.0-BETA2 on my laptop. While building different ports, i am encountering messages like the following (in particular the last line, the others are only warnings) > > /usr/bin/ld: warning: libstdc++.so.5, needed > by /usr/local/lib/libicui18n.so.36, may conflict with > libstdc++.so.6 > > /usr/bin/ld: warning: libm.so.4, needed > by /usr/local/lib/libicui18n.so.36, may conflict with libm.so.5 > > /usr/bin/ld: > warning: libm.so.4, needed by /usr/local/lib/libicui18n.so.36, may conflict > with libm.so.5 > > /usr/local/lib/compat/libpthread.so.2: undefined reference to > `__malloc_lock' gmake[1]: > > I don't ever remember getting this error before. I am pretty sure i'm using only binaries built on this machine for 7.0... have I missed anything? what's the cause of this error? > > FWIW, I have compat6x installed You missed the "portupgrade -fa" step of the upgrade from 6.x to 7.x. Those errors come from binaries linked to both 6.x and 7.x libraries. Kris