couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miles Fidelman (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1640) build instructions broken for Debian
Date Sun, 13 Jan 2013 20:32:13 GMT


Miles Fidelman commented on COUCHDB-1640:

Russell: This worked for me.  Thanks!  Interestingly, there is a similar problem in building
Erlang R15 - the wxwidgets library has a similar naming problem, requiring a symbolic link
to fix.

Robert/Dave:  I'm going to delete the virtual machine, and repeat the process from scratch,
documenting the steps as I go (and see how many of the dependencies can be addressed directly
from current Debian stable packages, vs. building from source).  Then....
- I'm happy to update the wiki - just set up the permission and let me know what I need to
- I also figure that I can write this up as an INSTALL.Debian.Squeeze file, for distribution
- let me know if this makes sense, and how to submit it.

> build instructions broken for Debian
> ------------------------------------
>                 Key: COUCHDB-1640
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Build System
>            Reporter: Miles Fidelman
>            Assignee: Dave Cottlehuber
> The instructions for building 1.2.1, from source, on Debian Stable (Squeeze) are completely
broken - both the INSTALL.Unix file in the distribution, and the wiki page at
> For one, the version of spidermonkey (libmozjs) is older than the minimum required for
Couch 1.2.1.
> For two, even after installing the latest spidermonkey from upstream, I can't get more
than half the developer tests to complete after an install.  I expect it has to do with path
issues and the proper invocation of ./configure - but I can't figure out what the magic incantation
> I kind of wonder if anybody has actually tried a full install on Debian Stable.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message