From: djberg96@... (Daniel Berger)
Date: 2003-01-12T12:07:53+09:00
Subject: Re: Statically linking ruby extensions - build problem

First off, my apologies for that last response.  Apparently, Phoenix
for BeOS has some problems with newlines.  I have no idea what
happened.

Daniel Carrera <dcarrera@math.umd.edu> wrote in message news:<Pine.GSO.4.44.0301111626460.791-100000@bezier.math.umd.edu>...
> 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.

Oh, ok.  Well, I didn't try that but I did try a simpler version of
sys-host and even that failed.

> 
> 
> > 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).

Actually, it is.  I think the format of my last post caused confusion.
 
> $ ls /boot/home/config/lib/ruby/site_ruby/1.8/i586-beos/sys
> 
> To verify it's there.  I'm sure it is.

Yes, it's definitely there.  I don't think it's a problem of seeing it
(I'd get  a "no such file" error in that case).  It just doesn't like
something about the shared object itself.

Any ld tips that might help?

Regards,

Dan