couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1640) build instructions broken for Debian
Date Sat, 12 Jan 2013 12:46:13 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551910#comment-13551910
] 

Robert Newson commented on COUCHDB-1640:
----------------------------------------

We'll work on the wiki page, and I can certainly give your wiki account permission to edit
if you would like to contribute.

CouchDB is packaged for Debian stable already, and CouchDB folks have assisted them in getting
a working libmozjs185-dev package into the next release specifically to support newer source-based
installs of CouchDB, a package which I believe installs cleanly on stable.


                
> build instructions broken for Debian
> ------------------------------------
>
>                 Key: COUCHDB-1640
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1640
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Build System
>            Reporter: Miles Fidelman
>
> 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 http://wiki.apache.org/couchdb/Installing_on_Debian
> 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
is.
> 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: http://www.atlassian.com/software/jira

Mime
View raw message