From: MenTaLguY <mental@...>
Date: 2006-03-23T04:48:19+09:00
Subject: Re: Ruby on HP-UX

I really think this approach of removing things until it compiles is a mistake; if you did eventually get something that built, you'd just end up with a build of Ruby that most likely won't run any useful Ruby scripts.

Your main issue is one of how the libraries Ruby depends on were built or installed -- you definitely do want to build them yourself, if you're currently trying to use prepackaged versions.  Part of the what's going on is missing header files, but I have no idea what else is going on.  If you build the libraries yourself with the default options (to the degree possible), they're a known quantity.

I actually created a /usr/local/ruby where I installed fresh builds of all the required libraries.  Note that doing so will required compiling everything with e.g. -Wl,+b -Wl,/usr/local/ruby/lib though...

Also, see my notes in the earlier post:
 http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/fdb97e11bcf2be54/d1dc4df9c0a875b8#d1dc4df9c0a875b8

I have to ask, though -- do you really need to do this on _HP-UX_?

For me, it was almost more pain than it was worth -- not because of adjustments required to Ruby itself, but because of quirks of the platform and the gymnastics required to build the libraries Ruby depends on in just the right way to make the dynamic linker happy.

-mental