unbroken dev/icu in current

Chris Rees crees at FreeBSD.org
Tue Jul 3 18:54:00 UTC 2012


On 3 July 2012 19:35, Ruslan Mahmatkhanov <cvs-src at yandex.ru> wrote:
> Chris Rees wrote on 03.07.2012 22:22:
>
>> On 3 July 2012 12:51, Rodrigo OSORIO <rodrigo at 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).
>

Great.... now I need to find an appropriate OSVERSION for marking
BROKEN on; I'm tempted to start with 1000000 and end with 1000014; if
no-one yells at me I'll commit it in an hour or so.

Chris


More information about the freebsd-ports mailing list