Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Aug 2004 23:48:06 +0300
From:      Ruslan Ermilov <ru@freebsd.org>
To:        Jeremy Messenger <mezz7@cox.net>
Cc:        ports@freebsd.org
Subject:   Re: x11-wm/fluxbox-devel having issues on recent -CURRENT?
Message-ID:  <20040814204806.GA99697@ip.net.ua>
In-Reply-To: <opscqgb1sy9aq2h7@mezz>
References:  <20040814171806.GB99032@ip.net.ua> <opscqgb1sy9aq2h7@mezz>

next in thread | previous in thread | raw e-mail | index | archive | help

--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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@FreeBSD.org> wrote:
>=20
> >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?
>=20
> Right now, I am working on upgrade my -CURRENT from June to today. I will=
 =20
> find out if I have the same problem as your this afternoon. I am planning=
 =20
> to do the 'rm -rf /usr/local/* /usr/X11R6/* /compat/linux/* /var/db/pkg/*=
' =20
> (I always do that) right after I am done with upgrade -CURRENT.
>=20
> Do you have mem and io in your kernel config as what in /usr/src/UPDATING=
 =20
> has said. They will be need for the X stuff.
>=20
Sure, I do.  My kernel is GENERIC based, with all extra
stuff removed.

$ 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
same problem.


Cheers,
--=20
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFBHnqGqRfpzJluFF4RAg7HAKCCABC8fb/fGGco6OitM4VcoKsWDQCbBWDi
GLb5erjUJZ6gddu+aqp0VRA=
=UHbq
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040814204806.GA99697>