Mac os x aclocal command not found

Macports or Brew should work too but I usually prefer a more minimalistic approach and build just what I need from source. The steps I described build the strict minimum to get automake working without duplicating any of the tools installed by Apple. If you can't find aclocal, check your path and how you invoke it.

Thanks for sharing. Three minutes copy-and-paste instead of hours try-and-error. Wishing you well!

Hi, i had problems with the. GNU Autoconf configure: GNU M4 1. Very useful. Xcode 4.

After running your script, when I try to run autoconf, I get the error: No such file or directory" Any ideas? This worked well for me on Mountain Lion Thank you. A quick comment, maybe replace autoconf Awesome post. Thanks much. Used it on For the person who had the M4 error, you need to install the Xcode command line tools now a Download under Preferences after you install xcode.

Or you could build your own m4 if you didn't want to download xcode. This was the top google result for "autoconf mac" when I realized Xcode on Mavericks didn't have it. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Navigation menu

Already on GitHub? Sign in to your account. There's a pull request against pixman to fix that error: On osx it seems that I needed to use brew to install "autoconf automake libtool". Not sure if this is relevant. However, I still am having trouble building servo. Submitting an additional issue.

I'm probably just doing something naive, but help would be appreciated. Ok, seems this is sufficient: I just cloned the repo and followed the instructions in the readme, and I'm still having the issue with the configure script looking for aclocal in the wrong place on my OS X The additional step added to the readme with doesn't seem to have helped.

Changing the configure script to look in the right place still nets an error, as there is no aclocal directory, just files. I'm sorry about all the build problems on OS X. I know it's really frustrating and am open to suggestions about how to make this build easier. For most of our 3rd-party submodules we rewrote the original makefiles to not use autotools, but spidermonkey and cairo are pretty big and it would be really nice to use their actual build system. I don't understand though how to consistently set up the correct build environment on OS X.

Perhaps instead of trying to use the upstream git repos and running autoconf we could use code from the release tarballs with the configure scripts already generated. Though I seem to recall trying that as well and deciding to run the autotools.

I actually got it built on OSX. I'm not sure what I did differently; all I did was change line of configure to:.

Your Answer

I have been unable to get past this issue on OSX Which version of OSX are you using semisight? I'm running I think I did that 3 or 4 times? Not sure if that would make a difference.. Cairo is gone now, and many build fixes have been checked in.