On 07/06/12 09:59, Ruslan Mahmatkhanov wrote:
Hi Rodrigo,
Rodrigo OSORIO wrote on 04.07.2012 00:33:
On 07/03/12 21:20, Ruslan Mahmatkhanov wrote:
Why to not just ask Rodrigo to update? I think this BROKEN is only
needed if icu doesn't builds on a system, that was installed from
official FreeB
On 07/03/12 20:35, Ruslan Mahmatkhanov wrote:
Chris Rees wrote on 03.07.2012 22:22:
On 3 July 2012 12:51, Rodrigo OSORIO 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 t
On 3 July 2012 20:20, Ruslan Mahmatkhanov wrote:
> Chris Rees wrote on 03.07.2012 22:53:
>
>> On 3 July 2012 19:35, Ruslan Mahmatkhanov wrote:
>>>
>>> Chris Rees wrote on 03.07.2012 22:22:
>>>
On 3 July 2012 12:51, Rodrigo OSORIO wrote:
>
>
>
> Hi,
>
> The port dev/i
Chris Rees wrote on 03.07.2012 22:53:
On 3 July 2012 19:35, Ruslan Mahmatkhanov wrote:
Chris Rees wrote on 03.07.2012 22:22:
On 3 July 2012 12:51, Rodrigo OSORIO 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
On 3 July 2012 19:35, Ruslan Mahmatkhanov wrote:
> Chris Rees wrote on 03.07.2012 22:22:
>
>> On 3 July 2012 12:51, Rodrigo OSORIO 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
Chris Rees wrote on 03.07.2012 22:22:
On 3 July 2012 12:51, Rodrigo OSORIO 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 thi
On 3 July 2012 12:51, Rodrigo OSORIO 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 w
