textproc/libxml2 does not install libxml2.so.5

[Marco Steinbach]

On Mon, 31 Oct 2011, b. f. wrote:

>>
>> This doesn't seem to do the trick for me:
>>
>> # echo $SHELL
>> /bin/csh
>> # setenv UNAME_r 9.9-CURRENT
>> # echo $UNAME_r
>> 9.9-CURRENT
>> # cd /usr/ports/textproc/libxml2
>> # make install clean
>> [...]
>> # pkg_info -g libxml2-2.7.8_1
>> Information for libxml2-2.7.8_1:
>>
>> Mismatched Checksums:
>> pkg_info: /usr/local/etc/xml2Conf.sh doesn't exist
>> pkg_info: /usr/local/lib/libxml2.so.5 doesn't exist
>> pkg_info: /usr/local/libdata/pkgconfig/libxml-2.0.pc doesn't exist
>>
>> Am I doing something wrong here ?
>>
>
> Yes, you are trusting us. ;)

Ah, and I thought it was something serious.

> There are a few problems related to the
> FreeBSD 10 fix that are still being worked out.  Whether or not the
> FreeBSD 10 fix is used depends on OSVERSION, which is calculated in
> bsd.port.mk, so your masquerading is incomplete:
>
>
>   1192 .if !defined(OSVERSION)
>   1193 .if exists(/usr/include/sys/param.h)
>   1194 OSVERSION!=     ${AWK}
> '/^\#define[[:blank:]]__FreeBSD_version/ {print $$3}' <
> /usr/include/sys/param.h
>   1195 .elif exists(${SRC_BASE}/sys/sys/param.h)
>   1196 OSVERSION!=     ${AWK}
> '/^\#define[[:blank:]]__FreeBSD_version/ {print $$3}' <
> ${SRC_BASE}/sys/sys/param.h
>   1197 .else
>   1198 OSVERSION!=     ${SYSCTL} -n kern.osreldate
>   1199 .endif
>   1200 .endif
> ...
>   3664 run-autotools-fixup:
>   3665 # Work around an issue where FreeBSD 10.0 is detected as
> FreeBSD 1.x.
>   3666 .if defined(WITH_FBSD10_FIX) && ${OSVERSION} >= 1000000
> ...
>
> You could edit the __FreeBSD_version line in param.h, or override
> OSVERSION on the command-line, setting it less than 1000000, if you
> wanted to continue to masquerade as 9.9 or some other suitable value
> while the problems are being resolved.

Thank you for your explanations, much appreciated -- miwi@ suggested another, different possible way in private mail (rebuilding devel/libtool, if I understood correctly), but I already had cleaned out all packages from the machine.

Not quite a sophisticated way of solving a problem, but it looks like it helped for now.

MfG CoCo