x11-wm/fluxbox-devel having issues on recent -CURRENT?
Jeremy Messenger
mezz7 at cox.net
Sat Aug 14 10:32:40 PDT 2004
On Sat, 14 Aug 2004 20:18:06 +0300, Ruslan Ermilov <ru at 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 at cox.net - mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome at FreeBSD.org
More information about the freebsd-ports
mailing list