On Wed, 2006-05-24 at 13:10 -0600, Andre T. wrote:
gcc and friends installed, but http11 didn’t compile properly…kernel
header sources needed for this ?? it just seems kinda strange for a
gem to require this stuff…
I’ll probably take this over to “mongrel-users”, not sure it’s still
appropriate for “rails”…but maybe good for the listmonger to index
for future people with same issue…
I actually use Ubuntu now just so I can suffer through all the crap
people have to put up with from the Debian packaging of Ruby. That’s
right, I suffer so everyone might get some relief.
First off, the pre-release (0.3.13) now checks to see if http11.so
actually built and spits out a nasty error message. This should help
with the silent denial from RubyGems when things fail.
Second, I have to write up the official Mongrel documentation on this
but here’s what got me started:
That whole series is really good, but this will get you a decent base
apache, php, mysql setup going. It’s a little dated but should help a
Then there’s this older documentation set, with these specific packages:
These instructions install a whole ton of stuff, so you might want to go
through them too. And remember that the stuff is old, so you’ll want to
confirm versions and such.
Then you’ll also want to install packages for readline, irb, ri, and
potentially ruby1.8-dev if that didn’t get installed. (I had to install
it, but other folks don’t). If you get really stuck and desperate then
you can try the shotgun approach:
sudo apt-get install
apt-cache search ruby | cut -d ' ' -f 1
But I really don’t suggest this. When all that’s done, then you should
go grab the source to RubyGems, install that manually (don’t use
debian’s since they install to weird locations IIRC).
Additionally, most people don’t even bother with Debian’s packages and
instead compile Ruby from source. I actually do this, but on my Ubuntu
machine I forced myself through the pain so I can write up some
Once you’ve done all that, I recommend that you complain to the package
maintainers to create a meta-package that allows you to build gems that
have compiled extensions in them.
The irony of the whole problem is if you bring up performance as a
complaint people go off about how you need to learn C and make
extensions and you’re a whiner. If you complain about how difficult it
is to setup Debian with a Ruby capable of building extensions the Debian
folks go off about how you’re an idiot and somehow carving a package
into 200 discrete pieces makes it easier to test (because we all know
that additional complexity makes things easier).
Since this is such a dichotomy with Ruby–and Mongrel is all about
making it easier for folks–I’ll hopefully have some documentation for
Mongrel users on this to match the Win32 documentation, but of course
it’ll be much much longer since even with Ubuntu it’s a royal pain to
get a decent development system going.
Let me know how far you get.
Zed A. Shaw