From: ts Date: 2002-07-26T19:38:49+09:00 Subject: Re: Search path for 'nested' .so files... >>>>> "G" == Gray, Jeff writes: G> * I am using a "private" installation of Ruby 1.6.7 (as opposed to our G> site installation of 1.6.5). The .so file was compiled using the G> makefile that was produced by a simple extconf.rb, but needed to G> be hacked a bit to get it to find/use the 1.6.7 libruby.so. This is G> relevant because using the site installation of 1.6.5 for both the G> Makefile generation and execution of the script produces a .so that G> doesn't have a LoadError. [It just core dumps, which is certainly my G> own fault. :^)] This is bad, try to avoid it. If you want to make a private version of ruby, compile it with ./configure --prefix=/directory/where/you/want/install/it Then be sure that this private version of ruby is find by the shell when you call ruby (PATH) Don't try to mix different versions of ruby Guy Decoux