libxml2 no longer compiles.

Jung-uk Kim jkim at FreeBSD.org
Wed Apr 10 18:18:50 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> [resending - incorrect subject and threading in previous reply]
> 
> William Palfreman wrote at 13:17 +0200 on Apr 10, 2013:
>> Hi.  This malinglist is listed as the maintainer for the libxml2
>> port. Doesn't seem to compile any more.
> [..]
>> .../../.libs/libxml2.so: undefined reference to `lzma_code'
> [..]
>> Have attached all the relevant txt config files and a list of 
>> installed apckages, whatever I can think of as this is -STABLE
>> and a
> [..]
>> lzmalib-0.0.1                  Thin wrapper library of LZMA
> [..]
> 
> You should usually include config.log from the working directory
> when reporting build problems.  You probably got this during 'make
> configure'...
> 
> checking for lzma_code in -llzma... no
> 
> .... which should perhaps be fatal for this port at configure
> time. But it's not, so you die later during at link time.
> 
> The culprit is the lzmalib port you have installed. It interacts
> badly in this case.
> 
> The quick fix is to remove that port if you don't need it. Then
> libxml2 will build.
> 
> A better fix might be to try to coerce libxml2 to use the base
> lzma include files & libs rather than the ones from lzmalib.  Here
> is a patch to do that...
> 
> Index: Makefile 
> ===================================================================
>
> 
- --- Makefile	(revision 315757)
> +++ Makefile	(working copy) @@ -28,8 +28,8 @@ 
> --with-html-dir=${PREFIX}/share/doc \ 
> --with-html-subdir=${PORTNAME} \ --without-python -CPPFLAGS+=
> -I${LOCALBASE}/include -LDFLAGS+=	-L${LOCALBASE}/lib +CPPFLAGS+=
> -I/usr/include -I${LOCALBASE}/include +LDFLAGS+=	-L/usr/lib
> -L${LOCALBASE}/lib
> 
> .if !defined(MASTERDIR) MAN1=		xml2-config.1 xmllint.1
> xmlcatalog.1

IMHO, we should get rid of CPPFLAGS and LDFLAGS altogether because
they serve no purpose here.

Jung-uk Kim

> Another might be to fix lzmalib to be a better wrapper.
> 
> Another might be to stop using lzmalib in our ports tree, fixing
> any references to it to just rely on the base lib instead and
> delete the lzmalib port.
> 
> Here is a closely related issue recently discussed on the list: 
> http://lists.freebsd.org/pipermail/freebsd-gnome/2013-April/028552.html
>
>  If no committer responds to this thread, please open a PR with
> this information.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAEBAgAGBQJRZaxnAAoJECXpabHZMqHOeSUH/Rz+xIzd8JqOEB7JKKFTRLUk
4KSt0gXQgdZjkdkkQv58q/FO0Slll3sqP+gN8tjnYTtUigqUTIrg9FkO5eI0OXuN
LmFeUeobLxDLNFsUN75kvnoiuVgA0RXwB26I45onPFDwJItkcZY3p9JLI+qF6VSx
hP2kuKZzIzf9xRbNITR2irtaC/GFYDPqHDJMn1myLJKM0ZH/ZQ3dkfXlqGnnQdlL
bbf4xpUhxQmjImunYLbWCdwKNArfZLBDqZVzts8znnG/Lk9K+0A3Bgp9RF+vHTAa
QL+UM8i73qjyuaBgxZ4mM48PKU8B9gYXrLID9Jc71a2TSX4pjQFOpY9h38u1W/g=
=jlW6
-----END PGP SIGNATURE-----


More information about the freebsd-gnome mailing list