1.4 Agent library dependencies (esp. libmysqlclient)

[Siegfried]

Hi,

I build some RPMS yesterday with 1.4 and the last spec file that I found in the forums that was for 1.3.5. The build worked fine and the packages are working, but I was wondering if it was normal that the agent got built with the same library dependencies as the server? The problem is that when I try to start the agent, it required both the curl library and the libmysqlclient. Is this expected? I thought I'd ask before and if there was a way to build it differently, without redoing a "configure" just for the client, as mysql is not needed on a lot of the boxes that we have.

Thanks

[abi]

hi,

weve had the same problem for the debian packages (the agent needlessly
linkin against mysql and the stuff), our solution was to run configure three
times,with different arguments (once with --enable-agent --with-ldap and
no other options, and twice with --enable-server [--with-mysql,
--with-pgsql] and the curl/net-snmp stuff)

Problem is the configure scripts add all linker flags to the agent
Makefile aswell.., you could of course hack the m4/configure scripts
to have seperate linker flags for the agent - but hey, that means work

We Build different packages for the components (zabbix-server-mysql,
zabbix-server-pgsql, zabbix-agent) which are only linked against
the libraries they are using ..

Since you cant link zabbix against both mysql and pgsql at the same
time and thus have to run configure twice anyway, the one configure
run for the agent doesnt matter .... at least not for us, as the packages
are beeing autobuild on the build daemons anyway.

You can have a look at our makefile:

http://svn.debian.org/wsvn/collab-maint/deb-maint/zabbix/branches/dev/debian/rules?op=file&rev=0&sc=0

of course there is much debian related stuff in there, but you might
get the overall idea