x11-wm/fluxbox-devel having issues on recent -CURRENT?
ru at freebsd.org
Sat Aug 14 13:48:18 PDT 2004
On Sat, Aug 14, 2004 at 12:32:15PM -0500, Jeremy Messenger wrote:
> On Sat, 14 Aug 2004 20:18:06 +0300, Ruslan Ermilov <ru at FreeBSD.org> wrote:
> >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.
Sure, I do. My kernel is GENERIC based, with all extra
$ file /dev/io /dev/mem
/dev/io: character special (248/14)
/dev/mem: character special (245/0)
Note that old fluxbox binary started exhibit this problem right
after a world/kernel upgrade. The new binary is exhibiting this
ru at FreeBSD.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040814/dfa03996/attachment.bin
More information about the freebsd-ports