-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation error about icu4c #3
Comments
I am unable to help you with anything specific to OSX but we've seen some issues when people have automake, autoconf and libtool somehow not 100% properly installed. What is output of the following: glibtoolize --version libtoolize --version autoconf --version automake --version on your box ? |
Thanks for responding so quickly! Here is the output: Nomad:couchbase-examples hansspeijer$ glibtoolize --version Copyright (C) 2010 Free Software Foundation, Inc. Written by David J. MacKenzie and Akim Demaille. Copyright 2006 Free Software Foundation, Inc. |
Something appear to be causing glibtoolize to not create ltmain.sh file that it's supposed to create. I am thinking that maybe this tool is somehow mis-installed or misconfigured. May I ask you for output of: which glibtoolize ? |
Nomad:couchbase-examples hansspeijer$ which glibtoolize I have to admit that this system has seen many build systems over the years. In particular I just installed homebrew and backed up macports. Does this help? Nomad:couchbase-examples hansspeijer$ brew doctor
Consider amending your PATH so that /usr/local/bin Warning: Your Homebrew is outdated. |
what if you try to follow brew's advice ? Particularly I just noticed that your system's autoconf is far from newest and same applies to libtool. |
It sure helps. I now get configure: will check for sigar.h in /Users/hansspeijer/Development/Projects/couchbase/install/include |
Doing much better now but still no sigar: Making install in tests Thanks for the help! |
make sure you have reasonably recent automake, autoconf and libtool installed (i.e. maybe via brew) |
also given you've switched tool versions it won't hurt to clean things that were produced by older tools. make clean-xfd-hard at top level will do that |
I think I found a problem, brew has installed newer versions then are currently used, will check my path |
I am a bit confused at the moment but we are getting there: Written by Tom Tromey [email protected] Copyright 2006 Free Software Foundation, Inc. |
do ls -l /usr/local/bin/automake to double check where it points. Your ln -s is not a force ln so maybe some symlink already exists there. Whether you actually need symlink I have no idea, maybe brew is supposed to do that for you. |
Thanks for your help Aliaksey. I am still experiencing strange behavior but it seems the only true 'bug' is my build environment and a small documentation error about icu4c. |
Ok, I managed to make it build. If we can just fix that small documentation issue about icu we can close this issue. |
Your bash was working "as designed". AFAIK there's some sort of caching about where particular command is found. Regarding documentation fix, please, feel free to submit it. Via gerrit at review.couchbase.org. |
Just note for future: I've managed to reproduce similar behaviour when my system has both |
After following the mac os X instructions I got the following error:
checking for icu-config... no
*** The icu-config script could not be found. Make sure it is
*** in your path, and that taglib is properly installed.
*** Or see http://ibm.com/software/globalization/icu/
configure: error: Library requirements (ICU) not met.
make: *** [couchdb/Makefile] Error 1
Which I fixed by doing
export PATH=
brew --cellar icu4c
/51.1/bin:$PATHinstead of
export PATH=
brew --cellar icu4c
/bin:$PATHas specified in https://github.com/membase/manifest/blob/master/README.markdown
The text was updated successfully, but these errors were encountered: