3

I have a shell script autogen.sh, I run it under my project directory in terminal:

./autogen.sh 

I get error:

Can't exec "glibtoolize": No such file or directory at /usr/local/Cellar/autoconf/2.69/share/autoconf/Autom4te/FileUtils.pm line 345, line 4.

Then, seems it can not find glibtoolize, so I tried to figure out where is my glibtoolize. Eventually, I find it is in this path:

/usr/local/Cellar/libtool/2.4.2/bin/glibtoolize

Then, I get stuck, how to solve my problem after I found my glibtoolize?

8

Looks like you already have libtool installed via brew but it is not linked so the required symlinks in /usr/local/bin are still missing. To create them,

brew link libtool
1

I ran into multiple problem while downloading protobuf. Try

brew install libtool

We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.

-3

I had the same problem after adding glibtoolize to the PATH variable it worked.

PATH=$PATH:/usr/local/Cellar/libtool/2.4.2/bin
export PATH
  • This just sets the path, which doesn't link anything. – nohillside Oct 27 '14 at 14:46
  • 1
    Also, you do not set a path to a specific file in bash. What you would do is set PATH=$PATH:/usr/local/Cellar/libtool/2.4.2/bin but that is still problematic because that method only sets one path to one thing in $PATH which is not ideal. – JakeGould Oct 27 '14 at 14:55
  • Ja, that is true, I changed my answer. In any case this solved my problem, as brew somehow did not make glibtoolize globally available. – Philiiiiiipp Oct 28 '14 at 15:43

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .