Ruby-Wordnet doesn't use any C components so it doesn't care where your
ruby.h is. The segfault in the distributed version is from an incorrect
use of BerkeleyDB's transactions, which is completely unrelated to the
Tiger problem.

Sorry for the confusion.