From owner-freebsd-ports@FreeBSD.ORG  Sun Dec 28 13:48:13 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 160F216A4CE
	for <freebsd-ports@freebsd.org>; Sun, 28 Dec 2003 13:48:13 -0800 (PST)
Received: from rutger.owt.com (rutger.owt.com [204.118.6.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0CCBB43D41
	for <freebsd-ports@freebsd.org>; Sun, 28 Dec 2003 13:48:10 -0800 (PST)
	(envelope-from kstewart@owt.com)
Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233])
	by rutger.owt.com (8.11.6p2/8.9.3) with ESMTP id hBSLm8u01050;
	Sun, 28 Dec 2003 13:48:08 -0800
From: Kent Stewart <kstewart@owt.com>
To: "Lee Harr" <missive@hotmail.com>, freebsd-ports@freebsd.org
Date: Sun, 28 Dec 2003 13:48:08 -0800
User-Agent: KMail/1.5.4
References: <BAY2-F115D5QxENQE6R0005649a@hotmail.com>
In-Reply-To: <BAY2-F115D5QxENQE6R0005649a@hotmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200312281348.08630.kstewart@owt.com>
Subject: Re: juk problem
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Dec 2003 21:48:13 -0000

On Sunday 28 December 2003 12:26 pm, Lee Harr wrote:
> Hi;
>
> After updating my ports the last time, juk no longer works. I get the KDE
> crash handler which ends up like this:
>
> (no debugging symbols found)...(no debugging symbols found)...
> 0x2939ed4c in __sys_poll () from /usr/lib/libc_r.so.4
> #0  0x2939ed4c in __sys_poll () from /usr/lib/libc_r.so.4
> #1  0x2939e298 in _thread_kern_sched_state_unlock () from
> /usr/lib/libc_r.so.4
> #2  0x2939dc5d in _thread_kern_scheduler () from /usr/lib/libc_r.so.4
> #3  0x0 in ?? ()
>
>
> I noticed while juk was building that there were some library conflicts
> (ie libvorbis, libvorbisfile, libogg and libmad were in both /usr/local/lib
> and in /usr/local/lib/compat/pkg)
>
> I tried removing the conflicting old libraries and rebuilding juk with
>
> portupgrade -Rf juk
>
> but I still have the same problem.  The system is a recent -stable.
>
> Do I need to use portupgrade -rRf ?
> Any other suggestions?
>

If you use KDE, you will need to force rebuild the dependancies of libvorbis. 
After I did that, I still saw messages about libvorbisfile.so.3 being 
missing, which I tracked down to coming from artsd when it would not start. 
When I portupgraded -uf arts, I had knotify sounds again with KDE.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html