FWIW, it almost worked for me. The compilation phase failed because it couldn't find unicode/ucol.h. So I ran ./configure again with:
CPPFLAGS=-I/opt/local/include ./configure --with-js-include=/opt/local/var/macports/software/spidermonkey/1.7.0_4/opt/local/include --with-js-lib=/opt/local/var/macports/software/spidermonkey/1.7.0_4/opt/local/lib and then it worked. Thanks for the instructions! -Nadav On Sat, Sep 12, 2009 at 11:28 AM, Trevor Turk <[email protected]> wrote: > I'm really not sure. Try just running sudo couchdb and see if everything > works. If so, there must be a permissions issue. I'm not too good with this > stuff, though, so at that point you might try the irc channel, or maybe > someone will reply here. In any case, please report back! I'm sure there are > more people having trouble than just us :) > > - Trevor > > > On Sep 12, 2009, at 10:47 AM, Justin Walgran <[email protected]> wrote: > > Trevor, >> Well done! Thanks. >> >> After running through your steps, I can launch couchdb using './utils/run' >> however when I try 'sudo -i couchdb couchdb' I get nothing. No crash, no >> console messages, nada. /usr/local/var/log/couchdb is empty. >> >> How can I find out what is choking the couchdb startup process? >> >> -Justin >> >> >> >> On Thu, Sep 10, 2009 at 11:45 PM, Trevor Turk <[email protected]> >> wrote: >> >> With the generous help of davisp in #couchdb, I was able to get >>> CouchDB working, it would seem, on Snow Leopard. >>> >>> I've done up some shoddy instructions on what I did here: >>> >>> http://pastie.org/613214 >>> >>> The basics are installing everything from MacPorts, then uninstalling >>> the couchdb port (which doesn't seem to work quite right). Then, you >>> install couchdb from source, fix the permissions, and set it up to >>> startup on boot. >>> >>> I think this should all be fine, but feedback is more than welcome. >>> >>> Thanks! >>> - Trevor >>> >>> -- Sincerely yours, Nadav
