From owner-freebsd-ports@FreeBSD.ORG Sat Aug 14 17:18:08 2004 Return-Path: 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 98F2F16A4CE; Sat, 14 Aug 2004 17:18:08 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9CA743D49; Sat, 14 Aug 2004 17:18:07 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i7EHI3JC049876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Aug 2004 20:18:04 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.12.11/8.12.11) id i7EHI7O8099129; Sat, 14 Aug 2004 20:18:07 +0300 (EEST) (envelope-from ru) Date: Sat, 14 Aug 2004 20:18:06 +0300 From: Ruslan Ermilov To: Jeremy Messenger Message-ID: <20040814171806.GB99032@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TRYliJ5NKNqkz5bu" Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: ports@FreeBSD.org Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Aug 2004 17:18:08 -0000 --TRYliJ5NKNqkz5bu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --TRYliJ5NKNqkz5bu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBHklOqRfpzJluFF4RAgrmAJ9MvK+2I0CmOwq7MtDYFykhgF3O4QCggo3w P3peExzZUjxe0A0kmWt8EjQ= =r/GQ -----END PGP SIGNATURE----- --TRYliJ5NKNqkz5bu--