Date: Tue, 03 Jul 2012 22:35:58 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: Chris Rees <crees@FreeBSD.org> Cc: Koop Mast <kwm@freebsd.org>, Rodrigo OSORIO <rodrigo@bebik.net>, freebsd-ports@freebsd.org Subject: Re: unbroken dev/icu in current Message-ID: <4FF33B8E.1000001@yandex.ru> In-Reply-To: <CADLo839Pxgr21SopyhyDV5KefSvp0HM2P58BJYG5Cmsz0uGtCw@mail.gmail.com> References: <20120703115119.GB49312@oldfaithful.bebik.local> <CADLo839Pxgr21SopyhyDV5KefSvp0HM2P58BJYG5Cmsz0uGtCw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Rees wrote on 03.07.2012 22:22: > On 3 July 2012 12:51, Rodrigo OSORIO <rodrigo@bebik.net> wrote: >> >> Hi, >> >> The port dev/icu fails to build in current due to an lock issue >> caused by the use of threads api. >> Disabling threads for icu in current solves the problem and the port >> can be build successfully and AFAIK this unbroke some of the ports who >> depends on icu. >> >> I don't know if this can be an acceptable short-term workaround for this >> por ? > > I've been reliably informed that icu builds just fine on CURRENT from > 1/July. I'll update my Tinderbox and let you know. > > Chris Can confirm that it builds without an issue on r237936 (Sun Jul 1 19:07:45 2012) with default option set (threads enabled). -- Regards, Ruslan Tinderboxing kills... the drives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FF33B8E.1000001>