pointyhat is building for 5.5 but claiming 8.0

Kris Kennaway kris at FreeBSD.org
Wed Jan 9 10:52:23 PST 2008


Boris Samorodov wrote:
> On Wed, 09 Jan 2008 00:28:45 +0100 Kris Kennaway wrote:
> 
>> Pav Lucistnik wrote:
>>> Boris Samorodov píše v st 09. 01. 2008 v 02:16 +0300:
>>>> On Tue, 08 Jan 2008 23:10:45 +0100 Pav Lucistnik wrote:
>>>>
>>>>>>> No, the port is using sysctl(2) to query the OS version which cannot
>>>>>>> be wrapped.
>>>>>> Hm, ports-mgmt/tinderbox masks it somehow... And doesn't get
>>>>>> an error for this port.
>>>>> The FreeBSD version inside the tinderbox is same as the host?
>>>> OK, I found the difference. The port builds for all FreeBSD version
>>>> except 5.x. The same is for ports-mgmt/tinderbox. Thus I think that
>>>> there is something that was not MFS'd to 5-STABLE that causes the
>>>> difference.
>>>>
>>>> For now I'm going to mark the port as IGNORE for OSVERSION < 600000.
>>>> A question to portmgr@: Do you have any objections?
>>> It would be nice to know what exactly is going on in there.
> 
>> Yeah, I can't imagine what it would be, unless it is using uname(1) or
>> (3) and 5.x doesn't have the environment variable overrides...but in
>> that case hundreds of other things would break.
> 
> I stepped a little bit further. Seems that the port (?) does not
> respect UNAME_r at 5.x (I have only 5.4-STABLE to test at):
> -----
> # echo $UNAME_r
> UNAME_r: Undefined variable.
> # uname -srm
> FreeBSD 5.4-STABLE i386
> # pwd
> /usr/ports/devel/py-lxml
> # make UNAME_r=9.0-FUTURE | grep freebsd
> creating build/lib.freebsd-5.4-STABLE-i386-2.4
> creating build/lib.freebsd-5.4-STABLE-i386-2.4/lxml
> copying src/lxml/_elementpath.py -> build/lib.freebsd-5.4-STABLE-i386-2.4/lxml
> copying src/lxml/ElementInclude.py -> build/lib.freebsd-5.4-STABLE-i386-2.4/lxml
> copying src/lxml/sax.py -> build/lib.freebsd-5.4-STABLE-i386-2.4/lxml
> copying src/lxml/__init__.py -> build/lib.freebsd-5.4-STABLE-i386-2.4/lxml
> creating build/temp.freebsd-5.4-STABLE-i386-2.4
> creating build/temp.freebsd-5.4-STABLE-i386-2.4/src
> creating build/temp.freebsd-5.4-STABLE-i386-2.4/src/lxml
> cc -fno-strict-aliasing -DNDEBUG -O -pipe -march=pentiumpro -DTHREAD_STACK_SIZE=0x20000 -O -pipe -march=pentiumpro -fPIC -I/usr/local/include -I/usr/local/include/libxml2 -I/usr/local/include/python2.4 -c src/lxml/etree.c -o build/temp.freebsd-5.4-STABLE-i386-2.4/src/lxml/etree.o -w
> ^C
> interrupted
> # 
> -----
> 
> Other FreeBSD versions (didn't check 6.x but assume the same):
> -----
> # echo $UNAME_r
> UNAME_r: Undefined variable.
> # uname -srm
> FreeBSD 8.0-CURRENT i386
> # pwd
> /usr/ports/devel/py-lxml
> # make UNAME_r=9.0-FUTURE | grep freebsd
> creating build/lib.freebsd-9.0-FUTURE-i386-2.5
> creating build/lib.freebsd-9.0-FUTURE-i386-2.5/lxml
> copying src/lxml/sax.py -> build/lib.freebsd-9.0-FUTURE-i386-2.5/lxml
> copying src/lxml/builder.py -> build/lib.freebsd-9.0-FUTURE-i386-2.5/lxml
> copying src/lxml/htmlbuilder.py -> build/lib.freebsd-9.0-FUTURE-i386-2.5/lxml
> copying src/lxml/_elementpath.py -> build/lib.freebsd-9.0-FUTURE-i386-2.5/lxml
> copying src/lxml/__init__.py -> build/lib.freebsd-9.0-FUTURE-i386-2.5/lxml
> copying src/lxml/ElementInclude.py -> build/lib.freebsd-9.0-FUTURE-i386-2.5/lxml
> creating build/temp.freebsd-9.0-FUTURE-i386-2.5
> creating build/temp.freebsd-9.0-FUTURE-i386-2.5/src
> creating build/temp.freebsd-9.0-FUTURE-i386-2.5/src/lxml
> cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x20000 -O2 -fno-strict-aliasing -pipe -fPIC -I/usr/local/include -I/usr/local/include/libxml2 -I/usr/local/include/python2.5 -c src/lxml/etree.c -o build/temp.freebsd-9.0-FUTURE-i386-2.5/src/lxml/etree.o -w
> ^Cinterrupted
> 
> # 
> -----
> 
> The same results are for adding "MAKE_ENV+= UNAME_r=9.0-FUTURE" to
> the port's Makefile.

Yes, 5.4 is likely too old.  How about 5.5?

Kris


More information about the freebsd-ports mailing list