Hi Justin, I got the same effect that you got, and after doing the following, mine's working now:
1. If you have ever followed http://wiki.apache.org/couchdb/Installing_on_OSX, and added the following to your path, you should remove it if you use Trevor's approach. export DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:/usr/local/spidermonkey/lib 2. After line 9 of Trevor's steps, I sudo port uninstall erlang, and build and install erlang from source by myself like the instruction in http://wiki.apache.org/couchdb/Installing_on_OSX (the snow leopard part). This may not be necessary, but it's what I did. 3. then proceed to line 10, build and install couchdb. Then it worked. Not sure if it would solve your problem, but it worked for me. -- Opscode, Inc. Nuo Yan, Software Development Engineer E: [email protected] On Sat, Sep 12, 2009 at 8: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 > > >
