Date: Sat, 14 Aug 2004 12:32:15 -0500 From: "Jeremy Messenger" <mezz7@cox.net> To: "Ruslan Ermilov" <ru@freebsd.org> Cc: ports@freebsd.org Subject: Re: x11-wm/fluxbox-devel having issues on recent -CURRENT? Message-ID: <opscqgb1sy9aq2h7@mezz> In-Reply-To: <20040814171806.GB99032@ip.net.ua> References: <20040814171806.GB99032@ip.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 14 Aug 2004 20:18:06 +0300, Ruslan Ermilov <ru@FreeBSD.org> wrote: > Hi! > > I've just upgraded my June 2004 -CURRENT, including > recompiling kernel, world, switching to X.Org, and > upgrading all other ports. All ports have been > forcibly recompiled, including those that didn't > change the version. > > Everything is fine so far, except for my WM, which is > fluxbox-devel -- it now fails with signal 10. Before > I upgraded ports, the old binary also exhibited this > same behavior (SIGBUS), and a recompile of all ports > didn't help. > > Can someone investigate or at least test/confirm this? Right now, I am working on upgrade my -CURRENT from June to today. I will find out if I have the same problem as your this afternoon. I am planning to do the 'rm -rf /usr/local/* /usr/X11R6/* /compat/linux/* /var/db/pkg/*' (I always do that) right after I am done with upgrade -CURRENT. Do you have mem and io in your kernel config as what in /usr/src/UPDATING has said. They will be need for the X stuff. Cheers, Mezz > Cheers, -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opscqgb1sy9aq2h7>