Date: Sun, 28 Dec 2003 13:48:08 -0800 From: Kent Stewart <kstewart@owt.com> To: "Lee Harr" <missive@hotmail.com>, freebsd-ports@freebsd.org Subject: Re: juk problem Message-ID: <200312281348.08630.kstewart@owt.com> In-Reply-To: <BAY2-F115D5QxENQE6R0005649a@hotmail.com> References: <BAY2-F115D5QxENQE6R0005649a@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312281348.08630.kstewart>