reopen 375810 thanks Hi Michael,
On Tue, Jul 25, 2006 at 02:12:45PM +0200, Michael Ablassmeier wrote: > > libssl-dev, zlib1g-dev > > well, those libaries are interlib-dependencys by other libraries zabbix > agent or zabbix server use (libldap_r for example depends on libgnutls > and libz stuff). ldd follows interlib-dependencies using ld.so with a > trace argument (it does load and link the binary), so it seems the > zabbix binaries would make use of those libraries in their code, they do > not. > > Both libssl-dev and zlib1g-dev are not used by any of the zabbix > components in a direct way, so they do not need to be listed in the > Build-Depends field.. Indirect dependencies are not followed by dpkg-shlibdeps (or at least it used to be this way). It seems that zabbix is explicitly checking for and linking with libz and libcrypto. Look at the logs: checking for compress in -lz... yes [...] checking for main in -lcrypto... yes [...] gcc -Wall -g -O2 -o zabbix_server [...] -lz [...] -lcrypto However (and this a more important fact that I overlooked), in the case of openssl it would be illegal to link a GPL program with it, since the OpenSSL developers added an advertising clausse that makes it incompatible. A Build-Conflicts should be present in order to avoid this from happening. Alternatively, you could link it with GnuTLS compat layer to see how it works out. -- Robert Millan ACK STORM, S.L. - http://www.ackstorm.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
