Hi Peter raspell is managed by Evan Weaver - you could try contacting him via GitHub: http://github.com/evan
I know he's pretty busy, so no idea how quickly he'll respond. -- Pat On 06/01/2010, at 4:33 AM, Peter Akkies wrote: > Hey Pat, > > I have been using those flags all along, and that unfortunately > doesn't solve the problem. I'd like to ask the Raspell author(s) for > support, but I can't figure out where I would do that. > > On Jan 5, 9:45 am, Pat Allan <[email protected]> wrote: >> Hi Peter >> >> When I've installed some gems (in particular, for MySQL and PostgreSQL) on >> my Snow Leopard setup, I've used some flags... and so far, they've worked >> smoothly, so maybe they'll help. Assuming you're using the standard bash >> shell: >> >> env ARCHFLAGS="-arch x86_64" gem install raspell >> >> It's also worth uninstalling raspell completely first, then re-installing. >> >> -- >> Pat >> >> On 05/01/2010, at 1:39 AM, Peter Akkies wrote: >> >> >> >>> Hi Pat, >> >>> After upgrading TS to the latest version I'm not getting the TS error >>> anymore. >> >>> Unfortunately, I still have the aspell/raspell trouble, and I did >>> actually recompile it, despite earlier having completely re-installed >>> macports for Snow Leopard. I'm fairly sure aspell is fine now, but I'm >>> worried about raspell. How can I check the architecture of the raspell >>> gem? >> >>> On Dec 12 2009, 9:14 am, Pat Allan <[email protected]> wrote: >>>> Hi Peter >> >>>> I think it's pretty safe to say that they're different problems... >> >>>> For the aspell/raspell one, have you copied aspell across from your >>>> Leopard install? I think it's definitely worth recompiling/installing from >>>> ports/brew again, and then un- and re-installing the gem (just to be sure). >> >>>> Still, even when that's sorted, I think the other error is going to come >>>> to the fore. Can you provide the full stacktrace? Also, what version of >>>> Rails are you using, and is the model in question involved in any STI or >>>> odd setup? What's the define_index block? >> >>>> -- >>>> Pat >> >>>> On 11/12/2009, at 4:41 PM, Peter Akkies wrote: >> >>>>> Well, Pat, I seem to have two problems. When I comment out the spell >>>>> check code, Thinking Sphinx gives me the the following error: >> >>>>> You have a nil object when you didn't expect it! >>>>> The error occurred while evaluating nil.constantize >> >>>>> Note that I am now using the gem; my gem config is the following: >> >>>>> # Thinking Sphinx and search spelling correction >>>>> config.gem 'thinking-sphinx', :lib => 'thinking_sphinx', >>>>> :version => '1.3.10' >>>>> config.gem 'raspell' >>>>> config.gem 'thinking-sphinx-raspell', :lib => 'thinking_sphinx/ >>>>> raspell', >>>>> :source => 'http:// >>>>> gemcutter.org', >>>>> :version => '>= 1.0.0' >> >>>>> When I do not comment out the spell check code, however, it is Aspell >>>>> that encounters a problem, which I suspect happens because I run Snow >>>>> Leopard. The error is the following: >> >>>>> dyld: lazy symbol binding failed: Symbol not found: _new_aspell_config >>>>> Referenced from: /Library/Ruby/Gems/1.8/gems/raspell-1.1/lib/ >>>>> raspell.bundle >>>>> Expected in: flat namespace >> >>>>> dyld: Symbol not found: _new_aspell_config >>>>> Referenced from: /Library/Ruby/Gems/1.8/gems/raspell-1.1/lib/ >>>>> raspell.bundle >>>>> Expected in: flat namespace >> >>>>> Trace/BPT trap >> >>>>> There is a thread on this problem here: >>>>> http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/... >> >>>>> This also shuts down my server. I don't quite know whether these are >>>>> two distinct problems or whether there is just one. In any case, when >>>>> I comment out the spell check, Thinking Sphinx should at least search, >>>>> but it does not. >> >>>>> Another note: I did not specify --sourcehttp://gemcutter.orgwhen >>>>> installing the gem, but the gem installed fine anyway, which I think >>>>> is because gemcutter is already in my source list. Just letting you >>>>> know in case that might matter. >> >>>>> -- >> >>>>> You received this message because you are subscribed to the Google Groups >>>>> "Thinking Sphinx" group. >>>>> To post to this group, send email to [email protected]. >>>>> To unsubscribe from this group, send email to >>>>> [email protected]. >>>>> For more options, visit this group >>>>> athttp://groups.google.com/group/thinking-sphinx?hl=en. >> >>> -- >> >>> You received this message because you are subscribed to the Google Groups >>> "Thinking Sphinx" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group >>> athttp://groups.google.com/group/thinking-sphinx?hl=en. > -- > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/thinking-sphinx?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en.
