USE="agent -curl -frontend -ipv6 -jabber -ldap -mysql -openipmi -oracle -postgres -proxy -server -snmp -sqlite3 -ssh" I traced the error and got the following patch: ===== BEGIN PATCH ========================================= --- m4/jabber.m4.old 2012-02-14 12:13:40.081473870 -0300 +++ m4/jabber.m4.new 2012-02-14 11:58:44.006445041 -0300 @@ -37,7 +37,7 @@ if test "x$_libiksemel_with" != x"no"; then if test "$_libiksemel_with" = "yes"; then - PKG_CHECK_MODULES(IKSEMEL,iksemel, + PKG_CHECK_MODULES=(IKSEMEL,iksemel, [ JABBER_INCDIR=$IKSEMEL_CPPFLAGS JABBER_LIBDIR=$IKSEMEL_LIBS ===== END PATCH =========================================== With that at least configures and compiles fine. The admin who asked for the installation is coming back in a couple of hours so I'm waiting for him to give me the configuration directives for the agent in order to test it and tell if it actually works. The following is the output I get: * Package: net-analyzer/zabbix-1.8.3 * Repository: gentoo * Maintainer: patrick@gentoo.org mattm@gentoo.org * USE: agent amd64 elibc_glibc kernel_linux multilib userland_GNU * FEATURES: sandbox * Adding group 'zabbix' to your system ... * - Groupid: next available * Adding user 'zabbix' to your system ... * - Userid: 101 * - Shell: /sbin/nologin * - Home: /var/lib/zabbix/home * - Groups: zabbix * - Creating /var/lib/zabbix/home in / * Applying zabbix-1.8.3-as-needed.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/net-analyzer/zabbix-1.8.3/work/zabbix-1.8.3' ... * Running aclocal -I m4 ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy ... [ ok ] checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes configure: Configuring checking whether make sets $(MAKE)... (cached) yes checking build system type... x86_64-pc-linux-gnu ··· checking for asprintf... yes checking for vsnprintf... yes checking for hstrerror... yes checking for getopt_long... yes checking for strcasestr... yes checking for getenv... yes checking for putenv... yes checking for -rdynamic linking option... yes ./configure: line 7927: syntax error near unexpected token `IKSEMEL,iksemel,' ./configure: line 7927: ` PKG_CHECK_MODULES(IKSEMEL,iksemel,' !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-analyzer/zabbix-1.8.3/work/zabbix-1.8.3/config.log * ERROR: net-analyzer/zabbix-1.8.3 failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 56: Called src_configure * environment, line 3873: Called econf '--disable-server' '--disable-proxy' '--enable-agent' '--disable-ipv6' '--without-ldap' '--without-net-snmp' '--without-mysql' '--without-pgsql' '--without-oracle' '--without-sqlite3' '--without-jabber' '--without-libcurl' '--without-openipmi' '--without-ssh2' * ebuild.sh, line 557: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of 'emerge --info =net-analyzer/zabbix-1.8.3', * the complete build log and the output of 'emerge -pqv =net-analyzer/zabbix-1.8.3'. * The complete build log is located at '/var/log/portage/build/net-analyzer/zabbix-1.8.3:20120214-132630.log.gz'. * The ebuild environment file is located at '/var/tmp/portage/net-analyzer/zabbix-1.8.3/temp/environment'. * S: '/var/tmp/portage/net-analyzer/zabbix-1.8.3/work/zabbix-1.8.3' Reproducible: Always
Ok, it works great with the patch!
Try a newer version. This one left the tree two months ago. If it still fails then, reopen but do paste your `emerge --info' output in a comment too.
Created attachment 302041 [details] Emerge --info
Well Jeroen Roovers, even with my tree outdated by months, net-analyzer/zabbix-1.8.7-r1 (neither in the tree now) compiles and works fine. Sorry for the inconvinience!
