couchdb @ 1.5.1: doesn't support erlang R17

[dbl001 (dbl)]

sudo port selfupdate
sudo port upgrade outdated # fails

sudo port clean couchdb
Password:
--->  Cleaning couchdb
David-Laxers-MacBook-Pro:lecture1 davidlaxer$ sudo port upgrade couchdb
--->  Computing dependencies for couchdb
--->  Fetching archive for couchdb
--->  Attempting to fetch couchdb-1.5.1_0.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/couchdb
--->  Attempting to fetch couchdb-1.5.1_0.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/couchdb
--->  Attempting to fetch couchdb-1.5.1_0.darwin_13.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/couchdb
--->  Fetching distfiles for couchdb
--->  Verifying checksums for couchdb
--->  Extracting couchdb
--->  Applying patches to couchdb
--->  Configuring couchdb
Error: Failed to configure couchdb, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_couchdb/couchdb/work/apache-couchdb-1.5.1/config.log
Error: org.macports.configure for port couchdb returned: configure failure: command execution failed
Please see the log file for port couchdb for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_couchdb/couchdb/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

Logfile opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_couchdb/couchdb/main.log:

:info:configure checking for curl-config... /opt/local/bin/curl-config
:info:configure checking for curl (libcurl 7.36.0) >= 7.18.0... yes
:info:configure checking Erlang version compatibility... configure: error: The installed Erlang version must be >= R14B (erts-5.8.1) and <R17 (erts-5.11)
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_couchdb/couchdb/work/apache-couchdb-1.5.1" && ./configure --prefix=/opt/local --enable-js-trunk
:info:configure Exit code: 1
:error:configure Failed to configure couchdb, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_couchdb/couchdb/work/apache-couchdb-1.5.1/config.log
:error:configure org.macports.configure for port couchdb returned: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
    while executing
"$procedure $targetname"
:info:configure Warning: targets not executed for couchdb: org.macports.install org.macports.configure org.macports.build org.macports.destroot
:notice:configure Please see the log file for port couchdb for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_couchdb/couchdb/main.log

[ci42]

CouchDB doesn't yet support Erlang R17. See: ​https://issues.apache.org/jira/browse/COUCHDB-2200

In the future please use WikiFormatting, Cc the maintainer and fill in the port field.

[jeff@…]

Patch attached that should take care of it. Based on what was done for the upstream ​COUCHDB-2200 ticket.

[petrrr]

Cc Me!

[posita (Matt Bogosian)]

The patch doesn't work for me in my prefix build. Logs (and my patched Portfile) are attached.

Notes:

• I have also applied the tweak from ticket:40360#comment:2 to my Portfile.
• I moved your patch's patch-support-erlang-R17.diff file into the files subdirectory of .../ports/databases/couchdb before doing a port build couchdb.

I can't quite figure this out, because I'm pretty sure everything appears to be where configure should be able to find it:

% ls -la /[[PREFIX]]/lib/erlang/usr/include
total 312
drwxr-s---  2 [[USER]]  [[USER]]    578 Apr 14 09:15 .
drwxr-s---  4 [[USER]]  [[USER]]    136 Apr 14 09:15 ..
-rw-r-----  1 [[USER]]  [[USER]]    972 Apr  7 11:31 driver_int.h
-rw-r-----  1 [[USER]]  [[USER]]  28535 Apr  7 11:31 ei.h
-rw-r-----  1 [[USER]]  [[USER]]    794 Apr  7 11:31 ei_connect.h
-rw-r-----  1 [[USER]]  [[USER]]    782 Apr  7 11:31 eicode.h
-rw-r-----  1 [[USER]]  [[USER]]  23740 Apr  7 11:31 erl_driver.h
-rw-r-----  1 [[USER]]  [[USER]]   1397 Apr  7 11:31 erl_drv_nif.h
-rw-r-----  1 [[USER]]  [[USER]]   3954 Apr  7 11:31 erl_fixed_size_int_types.h
-rw-r-----  1 [[USER]]  [[USER]]   1250 Apr 14 09:04 erl_int_sizes_config.h
-rw-r-----  1 [[USER]]  [[USER]]  14765 Apr  7 11:31 erl_interface.h
-rw-r-----  1 [[USER]]  [[USER]]   3917 Apr  7 11:31 erl_memory_trace_parser.h
-rw-r-----  1 [[USER]]  [[USER]]    851 Apr 14 09:04 erl_native_features_config.h
-rw-r-----  1 [[USER]]  [[USER]]   8084 Apr  7 11:31 erl_nif.h
-rw-r-----  1 [[USER]]  [[USER]]  28664 Apr  7 11:31 erl_nif_api_funcs.h
-rw-r-----  1 [[USER]]  [[USER]]   1356 Apr  7 11:31 erlang.idl
-rw-r-----  1 [[USER]]  [[USER]]  13549 Apr  7 11:31 ic.h

What I don't understand is this (from config.log):

configure:18661: result: no
configure:18661: checking erl_driver.h presence
configure:18661: /usr/bin/clang++ -E -I${exec_prefix}/lib/erlang/usr/include -I/usr/lib/erlang/usr/include -I/usr/local/lib/erlang/usr/include -I/opt/local/lib/erlang/usr/include -I/[[PREFIX]]/include -I/opt/local/include -I/usr/local/include -I/usr/include  conftest.cpp
conftest.cpp:40:10: fatal error: 'erl_driver.h' file not found
#include <erl_driver.h>
         ^
1 error generated.

Is configure not substituting the appropriate value for ${exec_prefix}, or am I just unfamiliar with reading configure logs?

[posita (Matt Bogosian)]

main.log from post-patch failed prefix build

[posita (Matt Bogosian)]

config.log from post-patch failed prefix build

[posita (Matt Bogosian)]

patched Portfile from failed prefix build

[jeff@…]

Replying to mtb19@…:

The patch doesn't work for me in my prefix build. Logs (and my patched Portfile) are attached.

Is configure not substituting the appropriate value for ${exec_prefix}, or am I just unfamiliar with reading configure logs?

That's what it looks like to me. I don't see how my changes for this would have caused it to be unable to find the erlang header files. Do you have a default macports setup to test on to see if this still happens for you without your prefix patches?

[jeff@…]

1.6.0 is pending release and it will support R17, so just close this.