Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Dec 2011 13:44:51 +0400
From:      Ruslan Mahmatkhanov <cvs-src@yandex.ru>
To:        Yuri Pankov <yuri.pankov@gmail.com>
Cc:        FreeBSD Ports Mailing List <ports@freebsd.org>, David Chisnall <theraven@FreeBSD.org>, gogo@cs.uni-sb.de
Subject:   Re: devel/py-lxml fails to build on 10.0-CURRENT
Message-ID:  <4EEB1313.101@yandex.ru>
In-Reply-To: <20111216093413.GC1751@procyon.xvoid.org>
References:  <4EEB0CB5.9090704@yandex.ru> <20111216093413.GC1751@procyon.xvoid.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EEB1313.101>