From owner-freebsd-x11@FreeBSD.ORG Wed Oct 24 04:57:44 2007 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94ED016A46B for ; Wed, 24 Oct 2007 04:57:44 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by mx1.freebsd.org (Postfix) with ESMTP id 7F01C13C4B2 for ; Wed, 24 Oct 2007 04:57:44 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from susy.dsl-verizon.net ([71.107.16.128]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JQE006K3GF7GE31@vms044.mailsrvcs.net> for freebsd-x11@freebsd.org; Tue, 23 Oct 2007 23:57:07 -0500 (CDT) Date: Tue, 23 Oct 2007 21:57:08 -0700 From: vehemens In-reply-to: <1193158470.1471.4.camel@rnoland-ibm.acs.internap.com> To: Robert Noland Message-id: <200710232157.08999.vehemens@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200709161632.32898.vehemens@verizon.net> <200710222115.56866.vehemens@verizon.net> <1193158470.1471.4.camel@rnoland-ibm.acs.internap.com> User-Agent: KMail/1.9.6 Cc: freebsd-x11@freebsd.org Subject: Re: Emerald Crashes (was: building compiz-fusion xml files from xml.in files) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2007 04:57:44 -0000 On Tuesday 23 October 2007 09:54:30 am you wrote: > On Mon, 2007-10-22 at 21:15 -0700, vehemens wrote: > > On Monday 22 October 2007 08:42:02 am Robert C. Noland III wrote: > > > On Mon, 2007-10-22 at 00:12 -0700, vehemens wrote: > > > > I'm attempting to build compiz-fusion from git, but unable to build > > > > the xml files. > > > > > > > > Anybody know what the trick is? > > > > > > See my response, re: bcop. I'll have 6.2/6.0 in ports in the next > > > couple of days. > > > > Got 6.0 working last Thursday or Friday. Dropped in with little pain and > > it works well expect for the emerald crashes. > > Which crashes, I have two machines both of which have been running > emerald without problems( on -current). I just built a fresh -current > laptop and currently emerald is frequently segfaulting when I close a > window. Specifically, If I close ccsm it hasn't failed to crash yet. > I'm thinking that it may have something to do with the CFLAGS that one > of my libraries was built with, but If that doesn't fix it, I'll be > looking hard at emerald... > > What are your symptoms? Any clear pattern? No pattern other then window closures. I saw a commit somewhere about staying with emerald 5.2. Haven't tried it myself.