Date: Thu, 22 Mar 2007 22:54:18 -0700 From: Ade Lovett <ade@freebsd.org> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: gnome@freebsd.org, Andrey Chernov <ache@freebsd.org>, Ade Lovett <ade@freebsd.org> Subject: Re: gettext problem (was Re: desktop-file-utils port problem) Message-ID: <43B097C8-C260-4DCA-8BE9-EE2F7C88A664@freebsd.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43B097C8-C260-4DCA-8BE9-EE2F7C88A664>