Github user micah commented on the pull request:

    https://github.com/apache/couchdb/pull/302#issuecomment-106585018
  
    ok, it seemed like I had a network glitch when the configure ran so the 
mango repository wasn't pulled, it now compiles fine. Now it is just a matter 
of resolving the make process to work without absolute paths, because right now 
what happens is this:
    
    ```
    ```
    install_dir = /usr/couchdb
    data_dir = /var/lib/couchdb
    view_index_dir = /var/lib/couchdb
    log_file = /var/log/couchdb.log
    user = couchdb
    ```
    
     then we have this issue:
    
    ```
    ==> rel (generate)
    WARN:  'generate' command does not apply to directory 
/home/micah/debian/couchdb/couchdb-2.0
    mkdir: cannot create directory ‘/usr/couchdb’: Permission denied
    Makefile:86: recipe for target 'install' failed
    make[1]: *** [install] Error 1
    make[1]: Leaving directory '/home/micah/debian/couchdb/couchdb-2.0'
    dh_auto_install: make -j1 install 
DESTDIR=/home/micah/debian/couchdb/couchdb-2.0/debian/couchdb 
AM_UPDATE_INFO_DIR=no returned exit code 2
    debian/rules:3: recipe for target 'binary' failed
    ```
    
    Thus, the install target in the Makefile fails because it tries to copy to 
an absolute path from the install.mk. To avoid this one needs to use 
[$DESTDIR](https://www.gnu.org/prep/standards/html_node/DESTDIR.html) so it 
will do things like this (for example):
    
    ```
    mkdir $(DESTDIR)$(install_dir)
    cp $(abs_top_srcdir)/foo/bar.erl $(DESTDIR)$(install_dir)/lib
    ```
    
    etc.
    
    This should be done in all places of install and uninstall. This also needs 
to be incorporated in the configure process. Once this is corrected I think I 
can continue to build a proper package.
    
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to