Date: Fri, 6 Apr 2007 23:38:09 -0700 From: Ade Lovett <ade@FreeBSD.org> To: Vijay Patel ((NewsLetters)) <patelvijayp.news@gmail.com> Cc: ports@FreeBSD.org, gnome@FreeBSD.org, kde@FreeBSD.org Subject: Re: gettext error Message-ID: <A1C214C1-C895-477A-A0A3-3E9CF3CB9EE7@FreeBSD.org> In-Reply-To: <003901c778d8$e53b8260$0100a8c0@team1> References: <003901c778d8$e53b8260$0100a8c0@team1>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 06, 2007, at 22:52 , Vijay Patel ((NewsLetters)) wrote: > Hello, > > I was also facing similar problem. & As per discussion of this > thread, its because, I am using FreeBSD 5.2 with latest > ports.tar.gz (As I am at remote location, FreeBSD upgrade is not > possible for me). > Here is how I solved problem of gettext. Here's the background. gettext-0.16.1 is now threads aware. In its current form, the port is indeed slightly broken, something that didn't come up during build and gnome-devel testing, and nork@ has kindly provided me with a patch. However, I have received isolated reports that the threaded-gettext is causing edge case issues with other ports. So, I am faced with something of a dilemma, since PORTREVISION will be bumped in either case (yes folks, y'all get to rebuild stuff, consider it a worldwide thrash-test of compilers ;) 1. Make devel/gettext respect PTHREAD_LIBS, and leave the threading in place 2. Disable threading entirely I'm open to either option here, and have taken the liberty of cc'ing the GNOME and KDE folks since they're very large consumers. -aDe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A1C214C1-C895-477A-A0A3-3E9CF3CB9EE7>