Not sure whether this is the right place to post this question or should I post it in Debian Squeeze thread, but anyway, I've Direct Admin installed on CentOS 5 which has been running for quite a while, however I'd like to switch towards Debian.
Now, I love custombuild and would like to keep using it, however it seems like eventhough some of the software is available on OS by default (zlib) custombuild is still trying to install its own zlib into /usr/local prefix.
While on CentOS it doesn't cause much of an issue as the version of zlib being installed by OS and custombuild are the same (1.2.3) on Debian it causes annoying warnings, like this one:
While its not a massive showstopper and I can simply manually relink those, I wanted to check what is the preferred method of working through this kind of issue.
Is there any specific reason why zlib provided by OS cannot be used (testing? I understand all testing is done against CentOS / RedHat)? The same situation goes with other libraries which are also available through distribution channels, i.e libpng, libcurl, libxml etc.
Any advice much appreciated.
Now, I love custombuild and would like to keep using it, however it seems like eventhough some of the software is available on OS by default (zlib) custombuild is still trying to install its own zlib into /usr/local prefix.
While on CentOS it doesn't cause much of an issue as the version of zlib being installed by OS and custombuild are the same (1.2.3) on Debian it causes annoying warnings, like this one:
Code:
# apt-get update
apt-get: /usr/local/lib/libz.so.1: no version information available (required by /usr/lib/libapt-pkg.so.4.10)
/usr/lib/apt/methods/http: /usr/local/lib/libz.so.1: no version information available (required by /usr/lib/libapt-pkg.so.4.10)
/usr/lib/apt/methods/http: /usr/local/lib/libz.so.1: no version information available (required by /usr/lib/libapt-pkg.so.4.10)
/usr/lib/apt/methods/http: /usr/local/lib/libz.so.1: no version information available (required by /usr/lib/libapt-pkg.so.4.10)
While its not a massive showstopper and I can simply manually relink those, I wanted to check what is the preferred method of working through this kind of issue.
Is there any specific reason why zlib provided by OS cannot be used (testing? I understand all testing is done against CentOS / RedHat)? The same situation goes with other libraries which are also available through distribution channels, i.e libpng, libcurl, libxml etc.
Any advice much appreciated.