I have found this interesting changelog comment from april about disabling the lintian warning for embedded zlib:
"erlang (1:13.a-dfsg-1) experimental; urgency=low
* New upstream beta release.
* Added packages libwxgtk2.8-dev, freeglut3-dev to build dependencies to make
wxErlang buildable.
* Split erlang-nox and erlang-x11 packages into a bunch of smaller packages
for individual Erlang/OTP applications. erlang-nox and erlang-x11 are still
exist and depend on the correspondent packages.
* Overridden lintian error 'embedded-zlib' because zlib included into Erlang
VM is patched, so using system-wide zlib will lead to unknown concequences.
* Bumped standards version to 3.8.1.
AFAIK no, because erlang's zlib is heavily patched :)"
The patching seems to be making zlib use different memory allocation routines. At the end of the thread there is a comment about possibly making it easier to use the system zlib in a future release.
I have found this interesting changelog comment from april about disabling the lintian warning for embedded zlib:
"erlang (1:13.a-dfsg-1) experimental; urgency=low
* New upstream beta release.
* Added packages libwxgtk2.8-dev, freeglut3-dev to build dependencies to make
wxErlang buildable.
* Split erlang-nox and erlang-x11 packages into a bunch of smaller packages
for individual Erlang/OTP applications. erlang-nox and erlang-x11 are still
exist and depend on the correspondent packages.
* Overridden lintian error 'embedded-zlib' because zlib included into Erlang
VM is patched, so using system-wide zlib will lead to unknown concequences.
* Bumped standards version to 3.8.1.
-- Sergei Golovan < <email address hidden>> Fri, 10 Apr 2009 16:32:04 +0400"
Also, I found this discussion thread:
http:// erlang. org/pipermail/ erlang- questions/ 2007-July/ 027700. html
"> is there an easy way to avoid building against erlang's internal zlib
> so the one from the system is used? If not, could a simple way be
> added?
>
> V-Li
>
AFAIK no, because erlang's zlib is heavily patched :)"
The patching seems to be making zlib use different memory allocation routines. At the end of the thread there is a comment about possibly making it easier to use the system zlib in a future release.