Hi I wondered if anybody had instructions on how to build couchdb 1.3.0? I'm failing miserably with:
I've looked at the v1.1 installation instructions and followed them (with newer versions of the dependancies) but I fail when attempting to make couchdb
I wondered if anybody could assist? Perhaps a WebFaction guru could build it ;-)
asked 10 May '13, 13:12
You can install using the same command as the previous guide except change the couchdb version.
answered 10 May '13, 17:01
Thanks to Timg for the answer to building version 1.3.0 of Couchdb. Unfortunately, I still got the same error. So out of curiosity I cut and pasted the version 1.1.1 instructions and guess what! I got the same error! So the problem doesn't appear to be with version 1.3.0 as such. Perhaps it is my environment? Any help would be greatly appreciated.
The error I got when building 1.1.1 is:
answered 11 May '13, 02:46
I've fixed it!!!
Short story: Clean out all of erlang detritus. Build again from scratch (using timg answer).
Longer story. When I first attempted the build of couchdb v1.3.0 I (foolishly?) decided to use the latest versions of all of the couchdb dependancies. One of the latest dependancies was R16 of erlang.
THAT R16 was the problem. It seems that epp:read_encoding/1 was introduced in R16 and of course earlier versions of compile.erl do not call that function. It looks like compile.beam is from R16 and epp.beam is from R15B03-1 or earlier.
However, trying to build an earlier version of erlang over the latest version didn't work as 'bits' were lying around so I just visually scanned the lib, bin etc directories for traces of erlang and deleted them. Then I rebuilt couch 1.3.0 from scratch but used the versions of the dependancies in the previous webfaction answer. Result? Happiness.
Thanks to timg for the time taken to answer my previous question.
answered 11 May '13, 03:25
The issue is that Erlang/OTP dropped support for parameterised modules, which CouchDB uses in its Mochiweb HTTP application. We've not put this into 1.3.0 as its a breaking change and will go into the next feature release instead.
If people are having trouble building from source in future, I strongly recommend reading the installation docs supplied in the source:
A fair number of dependencies changed in 1.3.0 so pay close attention!
answered 14 May '13, 11:32