From: eric.anderson@... (Eric Anderson)
Date: 2003-07-18T13:02:29+09:00
Subject: Re: ruby-mysql library load error

Brian Candler <B.Candler@pobox.com> wrote:
> You could try strace/truss/ktrace (depending on your OS) on ruby:
> 
>    strace ruby -r ./mysql.so
> 
> which should show you what files it's trying to access.

HA!! I figured it out. If you look at one of my previous posts, the
makefile generated does not actually compile mysql.c. From taking a
quick look at the extconf.rb file it looks like mysql.c is generated
from mysql.c.in after the makefile is created. So mysql.c doesn't yet
exist when the makefile is created causing the makefile to be
generated incorrectly.

A quick workaround is to run the extconf.rb script twice. This creates
a correct Makefile and compiles a library that I can include.

So now did I do something wrong on compiling this ruby module, or is
the extconf.rb script written incorrectly?

--
Eric Anderson