I did, but it wasn’t in all-caps. Once I did that, it built successfully.
However, it still fails to load. I tried with it included in ext/Setup and
with it commented out. It made no difference.
I tried a very simple extension as well just to make sure there wasn’t
something funky in my code - no luck.
I also tried setting the ac_default_path in the configure script to
/boot/home/config, just in case something was being hard-coded to /usr/local
somewhere. No luck.
BTW, the default path on BeOS should be /boot/home/config - this is what
most everything uses in BeOS. While it’s possible to create a /usr/local in
BeOS, it won’t survive a reboot - nothing manually generated in / survives.
In the meantime, I’ll see about getting a BeOS package installer made for
Ruby.
Regards,
Dan
···
-----Original Message-----
Hi,At Sun, 12 Jan 2003 03:05:39 +0900, > Daniel Berger wrote:
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.Did you make MANIFEST file?
–
Nobu Nakada