From owner-freebsd-ports@FreeBSD.ORG  Sat Aug 14 17:32:40 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B8F4716A4CE; Sat, 14 Aug 2004 17:32:40 +0000 (GMT)
Received: from lakermmtao02.cox.net (lakermmtao02.cox.net [68.230.240.37])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2D75243D49; Sat, 14 Aug 2004 17:32:40 +0000 (GMT)
	(envelope-from mezz7@cox.net)
Received: from mezz ([68.103.32.140]) by lakermmtao02.cox.net
          (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709)
          with ESMTP
          id <20040814173230.RBHC6588.lakermmtao02.cox.net@mezz>;
          Sat, 14 Aug 2004 13:32:30 -0400
Date: Sat, 14 Aug 2004 12:32:15 -0500
To: "Ruslan Ermilov" <ru@freebsd.org>
References: <20040814171806.GB99032@ip.net.ua>
From: "Jeremy Messenger" <mezz7@cox.net>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <opscqgb1sy9aq2h7@mezz>
In-Reply-To: <20040814171806.GB99032@ip.net.ua>
User-Agent: Opera M2/7.54 (Linux, build 751)
cc: ports@freebsd.org
Subject: Re: x11-wm/fluxbox-devel having issues on recent -CURRENT?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Aug 2004 17:32:40 -0000

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