Date: Mon, 5 Jan 2004 09:15:20 -0500 From: mi+mx@aldan.algebra.com To: Daniel Eischen <eischen@vigrid.com> Cc: current@freebsd.org Subject: Re: KDE stopped working after -current upgrade Message-ID: <200401050915.20710@misha-mx.virtual-estates.net> In-Reply-To: <Pine.GSO.4.10.10401050126240.28305-100000@pcnet5.pcnet.com> References: <Pine.GSO.4.10.10401050126240.28305-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Jan 2004, Mikhail Teterin wrote: => I had KDE running nicely since November on my dual PII. After => rebuilding -current on Saturday, I can not login -- seems like the => window manager is crashing: => => pid 52040 (kdeinit), uid 105: exited on signal 6 (core dumped) => => The only unusual thing is -- PTHREAD_LIBS is set to -lthr... I tried => rebuilding Qt, kdelibs, and kdebase -- still the same. =Ports are not yet ready for switching PTHREAD_LIBS to something other =than -lc_r. But don't let this stop you from trying to figure out which =ports are getting confused and fixing them :-) For 5.3 we'll need to =solve this since libkse^H^H^Hpthread will be the default. KDE ports seem to be ready. ldd confirms, that there is no -lc_r in the list of libraries -- only -lthr. Most importantly, it was running fine until the upgrade. I only started rebuilding it after noticing crashes post reboot. So, something broke over the month of December and -lthr (or its support in kernel) is my prime suspect. =FYI, the problem is that some ports have configure/libtools that =autodetect -lc_r and/or -pthread. So you may set PTHREAD_LIBS to -lthr =(or -lkse), but you'll end up linking to both -lthr and -lc_r. Use ldd =on the libraries/binaries and you'll see what I mean. Yes, I know. I went through that in November :-) -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200401050915.20710>