Missing zlib on latest ruby version

[fedzor]

You all know the error. missing require, blah blah. Seriously,
nothing new here. here's the scoop

But I found that zlib was missing from the latest ruby version on my
Ubuntu. I download and install from source the latest version, and
while installing rubygems, it complains of missing zlib!


Has anyone else experience this? This is also the case with the
version from March, as well.

-------------------------------------------------------|
~ Ari
".. NOT INTENDED FOR USE IN ... NUCLEAR FACILITIES, AIRCRAFT
NAVIGATION ... LIFE SUPPORT MACHINES" - iTunes EULA

 

[Jeffrey 'jf' Lim]

[Note: parts of this message were removed to make it a legal post.]

You all know the error. missing require, blah blah. Seriously, nothing new
here. here's the scoop

But I found that zlib was missing from the latest ruby version on my
Ubuntu. I download and install from source the latest version, and while
installing rubygems, it complains of missing zlib!

ruby doesnt depend on zlib, so ubuntu's correct. Only rubygems does. apt-get
install zlib1g

-jf

Has anyone else experience this? This is also the case with the version
from March, as well.

--
In the meantime, here is your PSA:
"It's so hard to write a graphics driver that open-sourcing it would not
help."
-- Andrew Fear, Software Product Manager, NVIDIA Corporation
http://kerneltrap.org/node/7228

 

[fedzor]

Yea, well. I'm extra dumb. Apparently the version installed through
apt-get contained the zlib package binary for itself only, which is
why it threw me for a loop. Needed to install zlib-devel system wide.

Fixed!

-------------------------------------------------------|
~ Ari
crap my sig won't fit

 

[Eric Hodel]

ruby doesnt depend on zlib, so ubuntu's correct. Only rubygems does.
apt-get
install zlib1g

Much like the readline, iconv, and openssl bindings, the zlib binding
is a part of ruby and like the others I mentioned, gets fairly
frequent use. In these respects, ruby (specifically, language,
library, and user community) does depend on them.

Furthermore, these C libraries are usually available on most operating
systems, so I find it reasonable to assume their ruby bindings are
available.

Making zlib (and similar libraries) an additional component that must
be found by the user causes confusion and creates a support burden for
people who have no idea what to do to fix it.

I've had various tickets filed against RubyGems because zlib or
openssl or rdoc was missing. It isn't my job to figure out a certain
platform requires extra installations just to get basic ruby
functionality, nor is it my job to track changes to package names and
installer arguments per platform, but I end up being the one who has
to deal with it.

I would be much happier if everybody's ruby worked reasonably the same
when they installed ruby, no matter the package system.

In this case, the problem was missing zlib headers, which falls under
the same general category of a support problem foisted onto
undeserving project maintainers.

 

[Jeffrey 'jf' Lim]

[Note: parts of this message were removed to make it a legal post.]

Much like the readline, iconv, and openssl bindings, the zlib binding is a
part of ruby and like the others I mentioned, gets fairly frequent use. In
these respects, ruby (specifically, language, library, and user community)
does depend on them.

hey - talk to the ubuntu (or whoever) guys.

Furthermore, these C libraries are usually available on most operating
systems, so I find it reasonable to assume their ruby bindings are
available.

Making zlib (and similar libraries) an additional component that must be
found by the user causes confusion and creates a support burden for people
who have no idea what to do to fix it.

I've had various tickets filed against RubyGems because zlib or openssl or
rdoc was missing. It isn't my job to figure out a certain platform requires
extra installations just to get basic ruby functionality, nor is it my job
to track changes to package names and installer arguments per platform, but
I end up being the one who has to deal with it.

I would be much happier if everybody's ruby worked reasonably the same when
they installed ruby, no matter the package system.

In this case, the problem was missing zlib headers, which falls under the
same general category of a support problem foisted onto undeserving project
maintainers.

I suppose i can imagine your pain. But hey, do up an faq if you really do
get that many support requests like that.

-jf

--
In the meantime, here is your PSA:
"It's so hard to write a graphics driver that open-sourcing it would not
help."
-- Andrew Fear, Software Product Manager, NVIDIA Corporation
http://kerneltrap.org/node/7228