From owner-freebsd-ports@FreeBSD.ORG Tue Jul 3 19:21:19 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF3FE1065674; Tue, 3 Jul 2012 19:21:19 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward16.mail.yandex.net (forward16.mail.yandex.net [IPv6:2a02:6b8:0:1402::1]) by mx1.freebsd.org (Postfix) with ESMTP id 1432E8FC08; Tue, 3 Jul 2012 19:21:19 +0000 (UTC) Received: from smtp19.mail.yandex.net (smtp19.mail.yandex.net [95.108.252.19]) by forward16.mail.yandex.net (Yandex) with ESMTP id 678C8D22509; Tue, 3 Jul 2012 23:21:17 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1341343277; bh=CPf8oGUIwHFz3Ryht+0xzrAdIiJj8Ybk1QyzF5RvA/0=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Ozasm4LOsF6nFhJd8Srze0lloHBVn+TgRzz4MKN8WRMhwrF3YiHuTmq8ud39QHJrK 7CPmVzNAeY2OFgw38grK4lFy2nwn6jcIJO11JFH/tKVAMvLiIViNMBid0LZLXTlskK 8lOuGAxZV5NVJ9ctN4syrH7V4jYk0MG8ai6q1MN0= Received: from smtp19.mail.yandex.net (localhost [127.0.0.1]) by smtp19.mail.yandex.net (Yandex) with ESMTP id 25E8ABE00E4; Tue, 3 Jul 2012 23:21:17 +0400 (MSK) Received: from unknown (unknown [178.76.224.133]) by smtp19.mail.yandex.net (nwsmtp/Yandex) with ESMTP id LGmWdTSZ-LGmuvKkD; Tue, 3 Jul 2012 23:21:16 +0400 X-Yandex-Rcpt-Suid: crees@FreeBSD.org X-Yandex-Rcpt-Suid: rodrigo@bebik.net X-Yandex-Rcpt-Suid: kwm@freebsd.org X-Yandex-Rcpt-Suid: freebsd-ports@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1341343277; bh=CPf8oGUIwHFz3Ryht+0xzrAdIiJj8Ybk1QyzF5RvA/0=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=thGtuoE1hl2jeAcURoX0whFdSZPGhh4qc4lbnEpITX5GD0y+UMBPuJSrAgF+CmA6F 5dpwQvlQa4VhO3aVVJ4eC3lNgUR+IzZ6xt9EgVXj8OTUGdRDMK6U6zN6EOM4wrsp0u NUqwTEC/mBjU7j6VGf5lua9nMgvRCijk2BgMFfTY= Message-ID: <4FF345E3.3050604@yandex.ru> Date: Tue, 03 Jul 2012 23:20:03 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120619 Thunderbird/13.0.1 MIME-Version: 1.0 To: Chris Rees References: <20120703115119.GB49312@oldfaithful.bebik.local> <4FF33B8E.1000001@yandex.ru> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Koop Mast , Rodrigo OSORIO , freebsd-ports@freebsd.org Subject: Re: unbroken dev/icu in current X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2012 19:21:19 -0000 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 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 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 FreeBSD -current snapshot. If memory serves me well there is many extra cautions in docs that using -current, csuped in wrong time, may produce various problems, so "It's a -current, babe" should sound reasonable, I believe. Is there any extra info (error logs), or was you able to reproduce it on some of your -current system? Rodrigo, can you please update your system and check if problem is gone? -- Regards, Ruslan Tinderboxing kills... the drives.