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

> BeOS 5.03 Pro

Cool.  Great to see another OS supported.  I've heard good things of BeOS.
I hope it grows.

> However, I can't seem to get my own extensions to
> load.  I'll take my own module, sys-uname, for
> example.  Seems to build fine - no errors or warnings.
>  Yet, when I try to 'require' it, I get a LoadError.

HHmmm... Try:

ruby -e 'puts $LOAD_PATH'

And see if it's looking for it in the right place.


> My next option was to try and statically link my
> extension into the ruby interpreter itself.  For this
> I turned to p.187 of the pickaxe, which says I should
> add an entry to the Setup file under /ext.  So, I
> created a "uname" directory under ext with the
> sys-uname contents, added an entry "uname" to the
> Setup and rebuilt.
>
> Unfortunately, it doesn't seem to work.  It never even
> attempts to build uname.

HHmmm... I don't know.
Did you ./configure again after you made the changes?
Does the new directory contain extconf.rb?

> Is this a BeOS specific issue or have the directions changed for 1.8.0?

I doubt either.

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