Date: Tue, 30 Oct 2007 19:56:21 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Christoph Friedrichs <christoph.friedrichs@helinet.de> Cc: freebsd-current@freebsd.org Subject: Re: Problem with libthr after update Message-ID: <47277E55.5060104@FreeBSD.org> In-Reply-To: <47270246.4020400@helinet.de> References: <47270246.4020400@helinet.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Christoph Friedrichs wrote: > Hi Guys, > > I?m relatively new with my freebsd -current box and actual experiencing > problems with starting kdm and portupgrade. Everytime I do so the > kdm-bin log explodes with this error messages: > > Fatal error 'Cannot allocate red zone for initial thread' at line 382 in > file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) > Fatal error 'Cannot allocate red zone for initial thread' at line 382 in > file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) > Fatal error 'Cannot allocate red zone for initial thread' at line 382 in > file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) > > I googled this problem and found something concering some ruby packages. > I did a manual rebuild of > > ruby-1.8.6_2,1 > perl-5.8.8 > ruby18-bdb-0.6.2 > db41-4.1.25_4 > portupgrade-2.3.1,2 > > With this rebuild problems with portupgrade were solved but kdm keeps > refusing to start with same error messages. In UPDATING I found this: > > 20071009: > Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and > WITHOUT_LIBTHR are set. > > Does this probably have something to do with this? Did you update from an older release of FreeBSD? Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47277E55.5060104>