[
https://issues.apache.org/jira/browse/COUCHDB-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600973#comment-13600973
]
Gennady commented on COUCHDB-1633:
----------------------------------
I've successfully installed couchdb 1.3 on Mac OS X via brew (as it was
suggested in provided gist). But command ./bootstrap still raises the same
error despite /usr/local/bin in right order in my shell PATH, imo (my echo
$PATH:
opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/sbin:/usr/local/mysql/bin)
> ./bootstrap error -> "Have you installed GNU Autoconf Archive?"
> ---------------------------------------------------------------
>
> Key: COUCHDB-1633
> URL: https://issues.apache.org/jira/browse/COUCHDB-1633
> Project: CouchDB
> Issue Type: Bug
> Components: Build System
> Reporter: Benoit Chesneau
> Assignee: Dave Cottlehuber
> Priority: Blocker
> Fix For: 1.3
>
> Attachments: locate.txt
>
>
> Something new with the build of couchdb I didn't have before. Now when
> launching bootstrap for the first time I get the following error:
> $ make
> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
> /Users/benoitc/work/couchdb/build-aux/missing --run aclocal-1.12 -I m4
> cd . && /bin/sh /Users/benoitc/work/couchdb/build-aux/missing --run
> automake-1.12 --foreign
> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
> /Users/benoitc/work/couchdb/build-aux/missing --run autoconf
> configure.ac:65: error: possibly undefined macro: AC_DEFINE
> If this token and others are legitimate, please use
> m4_pattern_allow.
> See the Autoconf documentation.
> configure.ac:326: error: possibly undefined macro: AC_MSG_WARN
> make: *** [configure] Error 1
> enlil:couchdb benoitc$ ./bootstrap
> Unable to find the `ax_check_icu.m4' file.
> Have you installed GNU Autoconf Archive?
> I solved it on ubuntu by installing autcoconf-archive. But I have no idea how
> to do the same thing on macosx yet. Also it should be documented so far.
--
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
