From owner-freebsd-ports@FreeBSD.ORG Fri Dec 16 09:45:19 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF5D91065675; Fri, 16 Dec 2011 09:45:19 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward14.mail.yandex.net (forward14.mail.yandex.net [IPv6:2a02:6b8:0:801::4]) by mx1.freebsd.org (Postfix) with ESMTP id 4878C8FC0A; Fri, 16 Dec 2011 09:45:19 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward14.mail.yandex.net (Yandex) with ESMTP id 9DA301982244; Fri, 16 Dec 2011 13:45:17 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1324028717; bh=vWaIdos25WonopMTWM5NwIhxQ4hLxr28iI7ixxXUdPA=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=FxCMRrt1k7qJOj+Bd6ecefvbJHp2/JGIlC9can0hP+cgw8r3ItLSlVcoXo1+B0WWF sEPmIqzVicXbREZ9UOrNMTNzm4XZQ4U4MWYdJ+mN478ykB1hljKoUAGxjc4ZRPT+nX Q8J11qGJ/7rffIw1dAovXbHdmoS+R2OIDMbDfO/Y= Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id 648A27E03E2; Fri, 16 Dec 2011 13:45:17 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1324028717; bh=vWaIdos25WonopMTWM5NwIhxQ4hLxr28iI7ixxXUdPA=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=FxCMRrt1k7qJOj+Bd6ecefvbJHp2/JGIlC9can0hP+cgw8r3ItLSlVcoXo1+B0WWF sEPmIqzVicXbREZ9UOrNMTNzm4XZQ4U4MWYdJ+mN478ykB1hljKoUAGxjc4ZRPT+nX Q8J11qGJ/7rffIw1dAovXbHdmoS+R2OIDMbDfO/Y= Received: from unknown (unknown [213.27.65.65]) by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTP id jGVWJgkS-jGVioWLe; Fri, 16 Dec 2011 13:45:17 +0400 X-Yandex-Spam: 1 Message-ID: <4EEB1313.101@yandex.ru> Date: Fri, 16 Dec 2011 13:44:51 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:8.0) Gecko/20111109 Thunderbird/8.0 MIME-Version: 1.0 To: Yuri Pankov References: <4EEB0CB5.9090704@yandex.ru> <20111216093413.GC1751@procyon.xvoid.org> In-Reply-To: <20111216093413.GC1751@procyon.xvoid.org> X-Enigmail-Version: undefined Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List , David Chisnall , gogo@cs.uni-sb.de Subject: Re: devel/py-lxml fails to build on 10.0-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: Fri, 16 Dec 2011 09:45:19 -0000 Yuri Pankov wrote on 16.12.2011 13:34: > On Fri, Dec 16, 2011 at 01:17:41PM +0400, Ruslan Mahmatkhanov wrote: >> Good day. >> >> I'm trying to build devel/py-lxml 2.3.2 (libreoffice dep) on >> 10.0-CURRENT with python27. Build fails like this: >> >> """ >> building 'lxml.etree' extension >> creating temp.freebsd-10.0-CURRENT-i386-2.7 >> creating temp.freebsd-10.0-CURRENT-i386-2.7/src >> creating temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml >> cc -DNDEBUG -O2 -pipe -fno-strict-aliasing -O2 -pipe >> -fno-strict-aliasing -fPIC -I/usr/local/include >> -I/usr/local/include/libxml2 -I/usr/local/include/python2.7 -c >> src/lxml/lxml.etree.c -o >> temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml/lxml.etree.o -w >> In file included from /usr/local/include/libxslt/xsltlocale.h:19, >> from /usr/local/include/libxslt/xsltInternals.h:24, >> from src/lxml/lxml.etree.c:265: >> /usr/include/xlocale.h:45: error: expected declaration specifiers or >> '...' before 'locale_t' >> """ >> >> Can anybody confirm that or it's just me? It builded just fine couple of >> weeks ago. Full buildlog here: >> http://people.freebsd.org/~rm/py-lxml.txt >> >> Thanks in advance. >> >> PS. I tried to rebuild libxslt/libxml2 to not avail. > > Same here. Probably related: > http://lists.freebsd.org/pipermail/svn-src-head/2011-November/031517.html > > > Yuri Good catch, Yuri! Thank you. David, would you suggest anything wrt this breakage? If this an upstream issue what exactly should i tell to upstream about the reason that trigger this breakage? Thank you. -- Regards, Ruslan Tinderboxing kills... the drives.