[ruby-talk:03923] There's still a problem with mod_ruby's Makefile.RB

Maybe I'm misunderstanding something here, but I build a non-shared
Ruby, then checked out the latest mod_ruby.

I ran

     ruby Makefile.RB --apxs=/tc/usr/apache/bin/apxs

And it generates a Makefile that contains:

     RUBY_INSTALL_NAME = ruby
     LIBRUBYARG = $(LIBRUBY_A)
     OBJS = mod_ruby.o ruby_config.o apachelib.o eruby.o
     TARGET = mod_ruby.so


LIBRUBYARG is invalid, as it hasn't been expanded into the path to my
libruby.a.

When I build mod_ruby, this results in a .so which does not have the
Ruby interpreter embedded. The link doesn't complain, because it's
building a shared library and is expecting to resolve the symbols at
load time. But as I don't have a shared Ruby, this won't happen.
Instead, I get a segv.

If I manually change the Makefile to set LIBRUBYARG to the full path
to libruby.a, my mod_ruby works fine.

Am I missing something, or is this a bug?


Regards


Dave