Ah, awesome! Great to hear that it was solved :) Cheers
-- Pat On 17/06/2009, at 2:47 PM, internetchris wrote: > > HAAAAAAA Halleluja! I can't beleive the self doubt cloud I've been in. > Ok with that said here's what fixed it... > > Your suggestions put me on the right track. I renamed those files and > they found the proper files in the usr/local/bin directory. That > didn't fix it however, but it definitely put me on the right track. I > don't remember doing a "sudo port install sphinx", but I'm sure I did. > This is my first mac and I probably followed the macport install > routine to get started. I issued a "sudo port uninstall" and then re- > installed everything manually using the guide at > http://mediumexposure.com/2009/05/01/installing-sphinx-postgres-leopard > . > Once I did that it worked great. It had to have been the confusion > between the manual and macport install. I'm not sure what exactly it > didn't like, but I'm extremely happy now. In fact I might take the > rest of the day off and revel in my satisfaction. > > Pat, I really appreciate your help and if you hadn't asked those > questions I'm not sure I would of found it. I will definitely > contribute to this success. I'm also going to post the solution on my > blog due to the fact the other 2-3 people I found on google with the > same problem never posted a solution. > > Thanks!!! > > Chris > > > > > > > On Jun 16, 11:28 pm, Pat Allan <[email protected]> wrote: >> Oh, and if my assumptions in the previous email are correct, you'll >> need to rename/delete the indexer binary under /opt as well - since >> that's the one that's actually complaining. >> >> -- >> Pat >> >> On 17/06/2009, at 1:10 AM, Pat Allan wrote: >> >> >> >> >> >>> Hi Chris >> >>> I don't want to build up hope too much, but I think that provides >>> the >>> answer - /opt is not where searchd defaults to installing to. From >>> memory though, it *is* where macports installs things. So I think >>> the >>> other installs have been working fine all this time, but the first >>> searchd (or last - not sure how bash preferences this) is the ports >>> install, not manual install. >> >>> My install (on a mac) is at /usr/local/bin/searchd -- if you have a >>> file there as well, try sudo renaming the one under /opt, fire up a >>> new shell (bash caches binary references, I think), and see if the >>> rake tasks are happy. >> >>> *fingers crossed* >> >>> And there's no charge for this support - paid work does generally >>> take >>> precendence for me (otherwise TS would be much more solid a beast). >>> That said, there is a pledgie, but no obligation to make any >>> payment. >>> This project has led to paid gigs in the past, and likely will in >>> the >>> future, and that's secondary to the satisfaction of having a library >>> out there that other people are happy about using, along with >>> general >>> recognition, kudos, etc. >> >>> Cheers >> >>> -- >>> Pat >> >>> On 16/06/2009, at 6:28 PM, internetchris wrote: >> >>>> Hi Pat, >> >>>> Ok so I got my computer back with a clean bill of health. With that >>>> said I ran the "which searchd" command from the terminal and got >>>> the >>>> following... >> >>>> /opt/local/bin/searchd >> >>>> I'm not sure if that helps you, let me know. In addition, you have >>>> been very generous with your time. If I need to reimburse you for >>>> you >>>> help I would be happy to do so. >> >>>> Thanks! >> >>>> Chris >> >>>> On Jun 14, 10:45 pm, internetchris <[email protected]> >>>> wrote: >>>>> Hi Pat, >> >>>>> I will give that a try. To update you on another issue my mac was >>>>> having.....I had it upgraded in regard to RAM about 2 weeks ago >>>>> and >>>>> every so often it would give me a strange beep in the middle of >>>>> using >>>>> it. This was strange to me so I took it back to the mac pro's this >>>>> weekend to have them look at it. It was strange enough that I >>>>> thought >>>>> maybe it was a contributing factor. It's not likely that these two >>>>> problems are related but it wouldn't be the first time I've seen >>>>> software affected by faulty RAM or hardware. As I said before I'm >>>>> grasping at straws, but thought I should "shore up" any other >>>>> wierd >>>>> issues. For how little I have used Thinking Sphinx I really like >>>>> it >>>>> and feel it's a very capable search option. I would rather figure >>>>> out >>>>> "my" problem and reep the benefits of using this search option. >> >>>>> As soon as I get my mac back I will give that command a try, and >>>>> also >>>>> re-install everything to see if anything changes. If this hardware >>>>> thing is the problem I should get some sort of "obscure problem >>>>> of >>>>> the year" award - lol. >> >>>>> Thanks, >> >>>>> Chris >> >>>>> On Jun 13, 2:41 pm, Pat Allan <[email protected]> wrote: >> >>>>>> What's the output of 'which searchd' on Terminal? Sounds like TS >>>>>> itself is fine. >> >>>>>> -- >>>>>> Pat >> >>>>>> On 13/06/2009, at 4:31 PM, internetchris wrote: >> >>>>>>> Hi Pat, >> >>>>>>> Yes sir, >> >>>>>>> I've been thinking though, I transferred all of my "working" >>>>>>> files >>>>>>> from my windows machine to the mac. Everything except the sphinx >>>>>>> install stuff. Could it be a problem with the TS installation? I >>>>>>> use >>>>>>> TS with Ruby on Rails so I beleive the only thing TS needs is >>>>>>> the >>>>>>> proper files in the vendor folder. The rake ts:config works just >>>>>>> fine >>>>>>> it's the rake ts:index that I have the problem with. >> >>>>>>> At this point I've been grasping at straws. >> >>>>>>> Thanks! >> >>>>>>> Chris >> >>>>>>> On Jun 13, 10:54 am, Pat Allan <[email protected]> >>>>>>> wrote: >>>>>>>> Hi Chris >> >>>>>>>> The output all looks correct to me - and yet you're still >>>>>>>> getting the >>>>>>>> same issues when running the rake tasks? >> >>>>>>>> -- >>>>>>>> Pat >> >>>>>>>> On 13/06/2009, at 12:33 PM, internetchris wrote: >> >>>>>>>>> Hi Pat, >> >>>>>>>>> I posted all of my output logs on the sphinx forum. Rather >>>>>>>>> than >>>>>>>>> jumble >>>>>>>>> up this post I thought I would have someone over there look at >>>>>>>>> the >>>>>>>>> logs as well. Here's the link so you can see the compile >>>>>>>>> process... >> >>>>>>>>> http://www.sphinxsearch.com/forum/view.html?id=3744 >> >>>>>>>>> I really appreciate your willingness to help. >> >>>>>>>>> Chris >> >>>>>>>>> On Jun 12, 5:06 pm, internetchris >>>>>>>>> <[email protected]> >>>>>>>>> wrote: >>>>>>>>>> Hi Pat, >> >>>>>>>>>> So I followed your advice with the same result. I actually >>>>>>>>>> had >>>>>>>>>> tried >>>>>>>>>> numerous times to re-install using new directories and such. >>>>>>>>>> This >>>>>>>>>> time >>>>>>>>>> I tried to install the beta version, but I'm still getting >>>>>>>>>> the >>>>>>>>>> same >>>>>>>>>> error. I am following the install example provided >>>>>>>>>> athttp://mediumexposure.com/2009/05/01/installing-sphinx-postgres-leopard >>>>>>>>>> . >>>>>>>>>> In my latest attempt I did everything the same, but I changed >>>>>>>>>> the >>>>>>>>>> file >>>>>>>>>> name for sphinx to use the latest beta. I'm soo stinking >>>>>>>>>> stumped >>>>>>>>>> on >>>>>>>>>> this problem. I am wondering if maybe it's a pathing issue? >>>>>>>>>> Is >>>>>>>>>> there >>>>>>>>>> anything I should provide in my pathe other than the >>>>>>>>>> "pg_config" >>>>>>>>>> file >>>>>>>>>> location? >> >>>>>>>>>> Your help has been outstanding I just wish I could give you >>>>>>>>>> good >>>>>>>>>> news. >> >>>>>>>>>> Thanks! >> >>>>>>>>>> Chris >> >>>>>>>>>> On Jun 10, 6:15 pm, Pat Allan <[email protected]> >>>>>>>>>> wrote: >> >>>>>>>>>>> Hi Chris >> >>>>>>>>>>> Just so we make sure that this isn't the cause, could you >>>>>>>>>>> download a >>>>>>>>>>> fresh version of the Sphinx source, run ./configure with the >>>>>>>>>>> command- >>>>>>>>>>> line args we've established work, and then 'make' and 'sudo >>>>>>>>>>> make >>>>>>>>>>> install'? I don't always trust recompiling within the same >>>>>>>>>>> folder. >> >>>>>>>>>>> Mind you, if that doesn't help matters, then we'll have to >>>>>>>>>>> find a >>>>>>>>>>> different approach to the problem. >> >>>>>>>>>>> Cheers >> >>>>>>>>>>> -- >>>>>>>>>>> Pat >> >>>>>>>>>>> On 10/06/2009, at 2:25 AM, Chris Sund wrote: >> >>>>>>>>>>>> Hi Pat, >> >>>>>>>>>>>> I gave that a try just as you instructed but no luck. I've >>>>>>>>>>>> seen >>>>>>>>>>>> some >>>>>>>>>>>> articles on 64bit installations, but to be honest I'm not >>>>>>>>>>>> sure >>>>>>>>>>>> how to >>>>>>>>>>>> tell if I have a 64bit machine. I'm new to my Mac, and I >>>>>>>>>>>> have >>>>>>>>>>>> actually >>>>>>>>>>>> tried the 64 bit instructions just to give it a try, but >>>>>>>>>>>> without >>>>>>>>>>>> luck. >>>>>>>>>>>> I know that I know when I get it figured out It will be >>>>>>>>>>>> something >>>>>>>>>>>> easy. Here's the last little bit of my ./configure >>>>>>>>>>>> output... >> >>>>>>>>>>>> configuring Sphinx >>>>>>>>>>>> ------------------ >> >>>>>>>>>>>> checking whether to compile with MySQL support... no >>>>>>>>>>>> checking whether to compile with PostgreSQL support... yes >>>>>>>>>>>> checking for pg_config... /opt/local/lib/postgresql83/bin// >>>>>>>>>>>> pg_config >>>>>>>>>>>> checking PostgreSQL C flags... -I/opt/local/include/ >>>>>>>>>>>> postgresql83 >>>>>>>>>>>> checking PostgreSQL linker flags... -L/opt/local/lib/ >>>>>>>>>>>> postgresql83 >>>>>>>>>>>> -lpq >>>>>>>>>>>> checking whether to use 64-bit document/word IDs... no >>>>>>>>>>>> checking whether to compile with libstemmer support... no >>>>>>>>>>>> checking for libexpat... found >>>>>>>>>>>> checking for libiconv... found >>>>>>>>>>>> checking for iconv() arg types... char ** >>>>>>>>>>>> checking for unaligned RAM access... yes >> >>>>>>>>>>>> generating configuration files >>>>>>>>>>>> ------------------------------ >> >>>>>>>>>>>> configure: creating ./config.status >>>>>>>>>>>> config.status: creating Makefile >>>>>>>>>>>> config.status: creating src/Makefile >>>>>>>>>>>> config.status: creating libstemmer_c/Makefile >>>>>>>>>>>> config.status: creating sphinx.conf.dist >>>>>>>>>>>> config.status: creating sphinx-min.conf.dist >>>>>>>>>>>> config.status: creating config/config.h >>>>>>>>>>>> config.status: config/config.h is unchanged >>>>>>>>>>>> config.status: executing depfiles commands >> >>>>>>>>>>>> configuration done >>>>>>>>>>>> ------------------ >> >>>>>>>>>>>> You can now run 'make' to build Sphinx binaries, >>>>>>>>>>>> and then run 'make install' to install them. >> >>>>>>>>>>>> As I said before, I really appreciate the help and any >>>>>>>>>>>> suggestions. >>>>>>>>>>>> I've done a ton of googling, and just can't find the right >>>>>>>>>>>> answer >>>>>>>>>>>> for >>>>>>>>>>>> my machine. I'm running Leopard 10.5.7. >> >>>>>>>>>>>> Chris >> >>>>>>>>>>>> On Jun 9, 10:35 pm, Pat Allan <[email protected]> >>>>>>>>>>>> wrote: >>>>>>>>>>>>> Hi Chris >> >>>>>>>>>>>>> I think the issue is that your initial compile is still >>>>>>>>>>>>> there, >>>>>>>>>>>>> and so >>>>>>>>>>>>> make won't recompile and replace them (I get caught on >>>>>>>>>>>>> this >>>>>>>>>>>>> sometimes >>>>>>>>>>>>> as well). I think 'make clean' should remove the compiled- >>>>>>>>>>>>> but- >>>>>>>>>>>>> not- >>>>>>>>>>>>> yet- >>>>>>>>>>>>> installed binaries... I don't know how to list the inputs >>>>>>>>>>>>> make >>>>>>>>>>>>> can be >>>>>>>>>>>>> given. >> >>>>>>>>>>>>> Try 'make clean', then the configure/make/sudo-make- >>>>>>>>>>>>> install >>>>>>>>>>>>> process >>>>>>>>>>>>> again. If there are no errors with ./configure, that >>>>>>>>>>>>> suggests >>>>>>>>>>>>> you're >>>>>>>>>>>>> on the right track. >> >>>>>>>>>>>>> Cheers >> >> ... >> >> read more ยป > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
