From: Daniel Carrera <dcarrera@...>
Date: 2003-01-12T06:57:48+09:00
Subject: Re: Statically linking ruby extensions - build problem

On Sun, 12 Jan 2003, Daniel Berger wrote:

> Oh, btw, I don't see a Test.c anywhere in the ruby source.  Is this
> something you just made up?

OOps, sorry.  Test.c is what I called the very first example in PickAxe.
It seems like a good test because it's just about the simplest extension
you can make.  Take a look at it.  You might want to try it.


> Ok, here's some more info:
>
> ruby -e 'puts $LOAD_PATH'
> /boot/home/config/lib/ruby/site_ruby/1.8
> /boot/home/config/lib/ruby/site_ruby/1.8/i586-beos
> /boot/home/config/lib/ruby/site_ruby
> /boot/home/config/lib/ruby/1.8
> /boot/home/config/lib/ruby/1.8/i586-beos

I notice that '.' is not present (but that doesn't matter for this
particular case).

[snip]
> Output of manually building uname in its own directory:
[snip]
> Seems to be in the load path.

Yes it does.  That's odd.  Try

$ ls /boot/home/config/lib/ruby/site_ruby/1.8/i586-beos/sys

To verify it's there.  I'm sure it is.

You could cd to that directory and try :

ruby -e 'require "uname"'

after adding '.' to the LOAD_PATH.  There's an environment variable todo
this, but I forget what it is.

Try the example from PickAxe.  I'll get back to you if I think of
anything.

Daniel Carrera
Graduate Teaching Assistant.  Math Dept.
University of Maryland.  (301) 405-5137