From owner-freebsd-gnome@FreeBSD.ORG Fri Mar 23 06:17:33 2007 Return-Path: X-Original-To: gnome@freebsd.org Delivered-To: freebsd-gnome@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B3D316A401; Fri, 23 Mar 2007 06:17:33 +0000 (UTC) (envelope-from ade@lovett.com) Received: from mail.lovett.com (foo.lovett.com [67.134.38.158]) by mx1.freebsd.org (Postfix) with ESMTP id 0B20913C480; Fri, 23 Mar 2007 06:17:33 +0000 (UTC) (envelope-from ade@lovett.com) Received: from hellfire.canal.lovett.com ([172.16.32.20]:64054) by mail.lovett.com with esmtpa (Exim 4.66 (FreeBSD)) (envelope-from ) id 1HUcjD-000DrH-Nc; Thu, 22 Mar 2007 22:54:19 -0700 In-Reply-To: <20070322101753.J72356@creme-brulee.marcuscom.com> References: <20070320054916.GA33710@nagual.pp.ru> <1174453429.79605.28.camel@shumai.marcuscom.com> <20070322034618.GB16823@nagual.pp.ru> <20070322063737.GA56493@nagual.pp.ru> <1174545988.8269.15.camel@shumai.marcuscom.com> <20070322124305.GA69324@nagual.pp.ru> <20070322101753.J72356@creme-brulee.marcuscom.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <43B097C8-C260-4DCA-8BE9-EE2F7C88A664@freebsd.org> Content-Transfer-Encoding: 7bit From: Ade Lovett Date: Thu, 22 Mar 2007 22:54:18 -0700 To: Joe Marcus Clarke X-Mailer: Apple Mail (2.752.2) Sender: ade@lovett.com Cc: gnome@freebsd.org, Andrey Chernov , Ade Lovett Subject: Re: gettext problem (was Re: desktop-file-utils port problem) X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2007 06:17:33 -0000 On Mar 22, 2007, at 07:19 , Joe Marcus Clarke wrote: > On Thu, 22 Mar 2007, Andrey Chernov wrote: >> Yes, adding --disable-threads to gettext completely fix the crash! > > Can you report this to Ade? Honestly, I'm not sure what to do about this. On the one hand, disabling thread support in devel/gettext is an option, but I don't know what ramifications that's going to cause for consumers of gettext that are threaded themselves. Right now, gettext is consumed by just over 1/3rd of all ports in the tree. This is the first report that I've seen where threads are apparently causing a problem, so I'm very reluctant to just go ahead and disable threads, bump PORTREVISION, and have everyone rebuild (almost) everything again. -aDe