Hi Rafe,
The C extensions should be loaded automatically. If there is an error,
Ferret 0.9.5 and earlier version will fall back an use the pure ruby
version. There won't be any error message printed to screen since
usually this will just be a result the extension not compiling
correctly.
If you aren't using acts_as_ferret you could try updating to the
0.10.0 gem. This will probably require a few changes as the API is not
backwards compatible. Otherwise I'd investigate why the extension
isn't getting loaded. Check that you definately have a ferret_ext.so
(or whatever the equavalent is on the mac, I think ferret_ext.bundle)
in your ferret gem directory in the ext folder. On my system (ubuntu)
it is /usr/lib/ruby/gems/1.8/gems/ferret-0.9.5/ext/ferret_ext.so. If
this file exists try;
require "ferret_ext"
Let us know how that goes.
Cheers,
Dave
On 8/23/06, Rafe Colburn <[EMAIL PROTECTED]> wrote:
> Thanks for the response. How do I get it to use the C extensions?
> They were compiled when I installed the Gem, so I assumed it was
> using them.
>
> --Rafe
>
> On Aug 22, 2006, at 1:25 PM, David Balmain wrote:
>
> > This may be due to a problem with the StandardAnalyzer regular
> > expression. It degrades exponentially on long tokens. If you must use
> > the pure ruby version of Ferret, try using a WhiteSpaceAnalyzer or a
> > LetterAnalyzer. I'd recommend using Ferret with the C extensions
> > whenever possible though.
>
> _______________________________________________
> Ferret-talk mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/ferret-talk
>
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
