schneuwlym commented on issue #3571:
URL: https://github.com/apache/couchdb/issues/3571#issuecomment-855716978


   Hi nickva, thanks for your reply.
   
   Indeed it seems that our packager patched the source to build couchdb
   ```
   --- a/src/couch/src/couch_emsort.erl.clean      2021-01-14 
17:18:40.436549175 +0000
   +++ a/src/couch/src/couch_emsort.erl    2021-01-14 17:17:39.128103923 +0000
   @@ -133,6 +133,8 @@
    -export([add/2, merge/1, merge/2, sort/1, iter/1, next/1]).
    -export([num_kvs/1, num_merges/1]).
   
   +-import(math, [ceil/1]).
   +
    -record(ems, {
        fd,
        root,
   --- a/src/couch/rebar.config.script.clean       2021-01-14 
17:28:34.570100193 +0000
   +++ b/src/couch/rebar.config.script     2021-01-14 19:06:56.523186136 +0000
   @@ -107,7 +107,7 @@
            };
        {unix, _} when SMVsn == "1.8.5" ->
            {
   -            "-DXP_UNIX -I/usr/include/js -I/usr/local/include/js",
   +            "-DXP_UNIX " ++ os:getenv("JS_CFLAGS"),
                "-L/usr/local/lib -lmozjs185 -lm"
            };
        {win32, _} when SMVsn == "60" ->
   @@ -164,7 +164,7 @@
    CouchJSEnv = case SMVsn of
        "1.8.5" ->
            [
   -            {"CFLAGS", JS_CFLAGS ++ " " ++ CURL_CFLAGS},
   +            {"CFLAGS", JS_CFLAGS ++ " " ++ CURL_CFLAGS ++ 
os:getenv("JS_CFLAGS")},
                {"LDFLAGS", JS_LDFLAGS ++ " " ++ CURL_LDFLAGS}
            ];
        _ ->
   
   ```
   
   But what I don't understand is, the dependency page 
(https://docs.couchdb.org/en/3.1.1/install/unix.html#dependencies) mentions 
Erlang OTP 19.x as requirement. Do I don't understand the line "Erlang OTP 
(19.x, 20.x >= 21.3.8.5, 21.x >= 21.2.3, 22.x >= 22.0.5)" or is this 
information wrong? Since it is comma sparated, I assumed that 19.x is fully 
supported...
   
   What Erlang version should we try? 22 or should we already try the latest, 
eg 24? Since 24 is not mentioned in the list I guess we should go with 22, 
right?
   
   Regards
   Mathias


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to