Note that there are some explanatory texts on larger screens.

plurals
  1. PORVM Error running 'requirements_smf_libs_install automake libtool',
    text
    copied!<p>I'm trying to add an installation of <code>ruby-1.9.3-p392</code>, and during the install when installing the required packages automake, libtool, I get the following:</p> <pre><code>Error running 'requirements_smf_libs_install automake libtool', please read /usr/local/rvm/log/ruby-1.9.3-p392/1366754296_package_install_automake_libtool.log </code></pre> <p>The log file looks like this: </p> <pre><code>[2013-04-23 15:42:42] requirements_smf_libs_install [ ] automake 1.13.1 ~ dependencies... [[32m✔[0m] automake 1.13.1 ~ dependencies [ ] automake 1.13.1 ~ fetch... [[32m✔[0m] automake 1.13.1 ~ fetch [ ] automake 1.13.1 ~ patch... [[32m✔[0m] automake 1.13.1 ~ patch [ ] automake 1.13.1 ~ preconfigure... configure.ac:24: warning: macro `AM_SILENT_RULES' not found in library configure.ac:372: warning: macro `AM_SUBST_NOTMAKE' not found in library configure.ac:24: error: possibly undefined macro: AM_SILENT_RULES If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:377: error: possibly undefined macro: AM_SUBST_NOTMAKE autoreconf: /opt/sm/pkg/versions/autoconf/2.69/bin/autoconf failed with exit status: 1 [[32m✔[0m] automake 1.13.1 ~ preconfigure [ ] automake 1.13.1 ~ configure... ERROR(__sm.package.error): Configuration of automake 1.13.1 failed. Tail of configure.log: ./configure: line 2006: syntax error near unexpected token `yes' ./configure: line 2006: `AM_SILENT_RULES(yes)' </code></pre> <p>I'm on Mac OSX Lion, with HomeBrew installed and brew doctor clean. The weirdest part is that automake and libtool have already been installed via Brew. It looks like this was an issue that RVM had but was supposedly fixed: <a href="https://github.com/wayneeseguin/rvm/issues/1803" rel="nofollow">https://github.com/wayneeseguin/rvm/issues/1803</a>, maybe not for this specific ruby gem? </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload