Date: Tue, 14 Apr 2020 06:14:06 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 245613] net-mgmt/zabbix44-server: Build fails with LIBXML2 enabled Message-ID: <bug-245613-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245613 Bug ID: 245613 Summary: net-mgmt/zabbix44-server: Build fails with LIBXML2 enabled Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: chris@chrullrich.net CC: pg@pakhom.spb.ru CC: pg@pakhom.spb.ru Flags: maintainer-feedback?(pg@pakhom.spb.ru) Zabbix 4.4.7 (actually 4.4.6) changed the way it detects libxml2. Instead of the apparently obsolescent xml2-config tool it now uses pkgconfig. The Zabbix source provides an autoconf module for using pkgconfig to detect libxml2. This module does not work with the port. >From the poudriere log: [00:00:05] --CONFIGURE_ENV-- [00:00:05] PKG_CONFIG=3Dpkgconf XDG_DATA_HOME=3D/wrk[...] $PKG_CONFIG is set (by USES=3Dpkgconfig) to the bare name of pkgconf without path. The m4 module from the Zabbix source (m4/libxml2.m4) then does this: if test -x "$PKG_CONFIG"; then [...] and falls over because it expects $PKG_CONFIG to include the path. >From what sense I can make of Zabbix's m4 module, it wants to look up pkg-config (pkgconf) first and remember the full path, but it skips this pa= rt because USES=3Dpkgconfig has defined $PKG_CONFIG already. Possible fix: Remove the definition of PKG_CONFIG from Uses/pkgconfig.mk. I suppose this could be predicated on an option to the USES so it won't break everything else. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245613-7788>