blocks|key|225996|text|这对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|225997|$+gem+uninstall+libv8
$+gem+install+therubyracer|code-block|syntax|javascript|225998|(非常感谢http://www.ruby-forum.com/topic/4306127)|offset|length|225999|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ruby-forum.com/topic/4306127^0|0|0|5|13|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

This worked for me:

<pre><code>$ gem uninstall libv8
$ gem install therubyracer
</code></pre>

(A big thanks to <a href="http://www.ruby-forum.com/topic/4306127">http://www.ruby-forum.com/topic/4306127</a>)

blocks|key|225618|text|最后，我使用therubyracer+0.11.0beta5作为解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|225619|使用therubyracer+(0.11.0beta5)|225620|在Gemfile上添加以下内容|225621|gem+'therubyracer',+'~>+0.11.0beta5'
group+:libv8+do
++gem+'libv8',+"~>+3.11.8"
end|code-block|syntax|javascript|225622|然后是bundle+install|offset|length|style|CODE|225623|Mac+OSX+10.8山狮|225624|entityMap^0|0|0|0|0|3|E|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|Y|8|@$M|Z|N|10|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

At last I use therubyracer 0.11.0beta5 as a solution.

Using therubyracer (0.11.0beta5) 

add following on Gemfile

<pre><code>gem 'therubyracer', '~&gt; 0.11.0beta5'
group :libv8 do
 gem 'libv8', "~&gt; 3.11.8"
end
</code></pre>

then <code>bundle install</code>

Mac OSX 10.8 Moutain Lion

blocks|key|2879463|text|对于任何在MacOSX10.8+Mountain+Lion上遇到这个问题的人，当尝试用gem+'therubyracer',+'0.11.0'升级他们的Gemfile时，只需升级系统libv8+gem就可以了(不需要卸载任何其他gem+)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|2879464|$+gem+update+libv8
$+bundle+install|code-block|syntax|javascript|2879465|编辑|2879466|如果您使用Travis-CI+(或位于其他服务器上的其他CI工具，我假设)，您还需要显式地将libv8+gem添加到您的Gemfile：|2879467|Gemfile|2879468|gem+'libv8',+'3.11.8.3'|2879469|然后像往常一样使用bundle+install。只需注意，libv8可能需要大量的时间来安装，我注意到它可能最终会导致使用Travis+CI's+timeout+limits，从而导致构建失败。你可以稍微减轻这一点，在你的构建中不包括开发环境gem：|2879470|.travis.yml|2879471|#+...
bundler_args:+--binstubs=./bundler_stubs+--without+development|2879472|更新|2879473|是的，我几乎所有的Travis构建都因此而超时和失败。如果有人知道解决这个问题的方法(我希望“降级therubyracer”是最后的手段)，请留下评论！|2879474|更新2|2879475|这可能并不适用于所有应用程序，但似乎我的Rails+3.2.9应用程序实际上并不需要therubyracer或libv8。在从我的Gemfile中删除这些宝石后，我确认我的规范通过了，再次推送给Travis，它成功地构建了。所以，我想摆脱这些宝石(如果你不确定你真的需要它们)至少值得一试。|2879476|更新3|2879477|感谢苹果确认，如果你使用MacOSX10.8+Mountain+Lion，你根本不需要therubyracer+gem，因为该操作系统已经捆绑了Paul+Annesley+JavaScriptCore，它自己的Javascript运行器。在最初回答的时候，我正在使用Snow+Leopard，因此需要它。|2879478|entityMap|0|LINK|mutability|MUTABLE|url|https://travis-ci.org/|1|http://about.travis-ci.org/docs/user/build-configuration/#Build-Timeouts|2|https://stackoverflow.com/users/430695/paul-annesley^0|17|S|2J|5|24|7|0|0|0|1A|5|1O|7|5|9|0|0|0|7|0|0|9|E|T|5|1P|Q|1|0|0|B|0|0|0|1D|C|0|0|16|C|1J|5|1T|7|0|0|17|C|20|D|2|0^^$0|@$1|2|3|4|5|6|7|1N|8|@$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|1U|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|6|7|1V|8|@]|E|@]|F|$]]|$1|N|3|O|5|6|7|1W|8|@$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|D]]|E|@$9|21|A|22|1|23]]|F|$]]|$1|P|3|Q|5|6|7|24|8|@$9|25|A|26|B|D]]|E|@]|F|$]]|$1|R|3|S|5|I|7|27|8|@]|E|@]|F|$J|K]]|$1|T|3|U|5|6|7|28|8|@$9|29|A|2A|B|C]|$9|2B|A|2C|B|C]]|E|@$9|2D|A|2E|1|2F]]|F|$]]|$1|V|3|W|5|6|7|2G|8|@$9|2H|A|2I|B|D]]|E|@]|F|$]]|$1|X|3|Y|5|I|7|2J|8|@]|E|@]|F|$J|K]]|$1|Z|3|10|5|6|7|2K|8|@]|E|@]|F|$]]|$1|11|3|12|5|6|7|2L|8|@$9|2M|A|2N|B|C]]|E|@]|F|$]]|$1|13|3|14|5|6|7|2O|8|@]|E|@]|F|$]]|$1|15|3|16|5|6|7|2P|8|@$9|2Q|A|2R|B|C]|$9|2S|A|2T|B|C]|$9|2U|A|2V|B|D]]|E|@]|F|$]]|$1|17|3|18|5|6|7|2W|8|@]|E|@]|F|$]]|$1|19|3|1A|5|6|7|2X|8|@$9|2Y|A|2Z|B|C]]|E|@$9|30|A|31|1|32]]|F|$]]|$1|1B|3|-4|5|6|7|33|8|@]|E|@]|F|$]]]|1C|$1D|$5|1E|1F|1G|F|$1H|1I]]|1J|$5|1E|1F|1G|F|$1H|1K]]|1L|$5|1E|1F|1G|F|$1H|1M]]]]

For anyone encountering this issue on Mac OSX 10.8 Mountain Lion when attempting to upgrade their Gemfile with <code>gem 'therubyracer', '0.11.0'</code>, just upgrading the system <code>libv8</code> gem worked for me (no uninstallation of any other gem necessary):

<pre><code>$ gem update libv8
$ bundle install
</code></pre>

<h3>Edit</h3>

If you use <a href="https://travis-ci.org/" rel="nofollow noreferrer">Travis-CI</a> (or other CI tools located on other servers, I assume), you will need to explicitly add the <code>libv8</code> gem to your Gemfile as well:

Gemfile

<pre><code>gem 'libv8', '3.11.8.3'
</code></pre>

then <code>bundle install</code> as usual. Just note that <code>libv8</code> can take a significant amount of time to install and I've noticed that it may end up being the cause of going over <a href="http://about.travis-ci.org/docs/user/build-configuration/#Build-Timeouts" rel="nofollow noreferrer">Travis CI's timeout limits</a>, causing your build to fail. You can mitigate this slightly be not including development environment gems in your builds:

.travis.yml

<pre><code># ...
bundler_args: --binstubs=./bundler_stubs --without development
</code></pre>

<h3>Update</h3>

Yep, pretty much all my Travis builds timeout and fail because of this. If anyone knows a way to solve this problem (I would hope "downgrade <code>therubyracer</code>" is a last resort), please leave a comment!

<h3>Update 2</h3>

This may not work for all apps, but it seems that my Rails 3.2.9 apps didn't actually need <code>therubyracer</code> or <code>libv8</code> after all. After removing those gems from my Gemfile, I confirmed that my specs passed, pushed again to Travis and it built successfully. So, I guess getting rid of those gems (if you're not sure you actually need them) is at least worth a try.

<h3>Update 3</h3>

Thanks to <a href="https://stackoverflow.com/users/430695/paul-annesley">Paul Annesley</a> for confirming that if you're on Mac OS X 10.8 Mountain Lion, you don't need <code>therubyracer</code> gem at all since the OS already comes bundled with Apple JavaScriptCore, its own Javascript runner. At the time of the original answer, I was on Snow Leopard and hence needed it.

blocks|key|227941|text|也犯了同样的错误，这对我是有效的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|227942|在控制台中添加Gemfile：gem+uninstall+libv8|offset|length|style|CODE|227943|In+|unordered-list-item|227944|，添加以下内容：|ordered-list-item|227945|227946|227947|gem+'therubyracer'，:platforms+=>+:ruby，:require+=>+'v8‘gem+'libv8'，'~>+3.11.8’#根据需要从控制台更新版本号|227948|：libv8|227949|227950|如果您正在升级therubyracer+gem，那么在升级之后，您可能也想运行bundle+update+therubyracer。(考虑指定版本号)|227951|这是在Mac+10.6+(Snow+Leopard)上。|227952|entityMap^0|0|F|J|0|0|0|0|0|0|0|0|13|Q|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|15|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|18|8|@]|9|@]|A|$]]|$1|R|3|S|5|J|7|19|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Z|$]]

Had the same error, this worked for me:

<ol>
<li>From console: <code>gem uninstall libv8</code></li>
<li>In your Gemfile, add the following:

<pre><code>gem 'therubyracer', :platforms =&gt; :ruby, :require =&gt; 'v8'
gem 'libv8', '~&gt; 3.11.8' # Update version number as needed
</code></pre></li>
<li>From console: <code>bundle install</code></li>
</ol>

If you were in the middle of upgrading therubyracer gem, you may want to run <code>bundle update therubyracer</code> after that as well. (Consider specifying a version number)

This was on Mac 10.6 (Snow Leopard).

blocks|key|2879540|text|OSX+10.8.2，ruby+1.9.3p125|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2879541|以上这些对我来说都不起作用。我厌倦了试图为我的环境找到合适的gem，所以我只是软链接到这个缺失的g%2B%2B目标：|2879542|sudo+ln+-s+`which+g%2B%2B`+/usr/bin/g%2B%2B-4.2|code-block|syntax|javascript|2879543|对远程部署没有帮助，但可以在我的工作站上完成工作。|2879544|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

OSX 10.8.2, ruby 1.9.3p125

None of the above worked for me... I got tired of trying to find the right gem for my environment, so I just soft linked to the g++ target this things was missing:

<pre><code>sudo ln -s `which g++` /usr/bin/g++-4.2
</code></pre>

Not as helpfully for remote deployments, but get the job done on my workstation.

blocks|key|2879546|text|gem+uninstall+libv8
brew+install+v8
gem+install+therubyracer|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2879547|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>gem uninstall libv8
brew install v8
gem install therubyracer
</code></pre>

blocks|key|227960|text|但是，你会问，为什么会发生这种情况？为什么卸载libv8并重新安装therubyracer就能解决这个问题？|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|227961|答案在错误消息的底部(来自orig+post)。忽略有关的内容|227962|probably+lack+of+necessary+libraries+and/or+headers|code-block|syntax|javascript|227963|无论是谁写了这条错误消息，这都是一个错误的假设。在底部，您可以看到Ruby对此有什么看法：|227964|undefined+method+`include_path'+for+Libv8:Module|227965|在我的例子中，我试图用bundle+install安装therubyracer-0.9.8，出于某种原因，它试图使用我的libv8-3.11.8.13副本，该副本在某个时刻已经安装，可能是其他gem的依赖项。|227966|我不知道为什么它要尝试使用较新的版本，因为therubyracer.gemspec包含s.add_dependency+"libv8",+"~>+3.3.10"。我的Gemfile.lock说要用libv8+(3.3.10.2)。但天哪，这确实是正在发生的事情。|227967|确实，Libv8:Module在libv8-3.11.8.13中没有include_path方法，但在libv8-3.3.10.2中有|227968|这就是为什么卸载所有版本的libv8，然后重新安装therubyracer的原因。因为所有不具有方法include_path的libv8版本都会被完全删除，并且在重新安装therubyracer时会重新安装具有方法include路径的libv8。|227969|entityMap^0|N|5|X|C|0|0|0|0|0|B|E|R|I|1O|F|0|L|K|17|11|2B|C|2Q|G|0|3|C|G|F|Y|C|1F|E|0|D|5|P|C|1E|C|1R|5|2D|C|2Z|7|39|5|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|18|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1P|8|@$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]]|D|@]|E|$]]|$1|W|3|X|5|6|7|1Y|8|@$9|1Z|A|20|B|C]|$9|21|A|22|B|C]|$9|23|A|24|B|C]|$9|25|A|26|B|C]|$9|27|A|28|B|C]|$9|29|A|2A|B|C]|$9|2B|A|2C|B|C]]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|2D|8|@]|D|@]|E|$]]]|Z|$]]

But, why is this happening, you ask? And why does uninstalling <code>libv8</code> and reinstalling <code>therubyracer</code> fix the problem?

The answer is at the bottom of the error message (from orig post). Ignore the stuff about

<pre><code>probably lack of necessary libraries and/or headers
</code></pre>

This is an incorrect assumption by whoever wrote that error message. At the bottom, you see what Ruby has to say about it:

<pre><code>undefined method `include_path' for Libv8:Module
</code></pre>

In my case, I was trying to install <code>therubyracer-0.9.8</code> with <code>bundle install</code>, and for some reason, it was trying to use my copy of <code>libv8-3.11.8.13</code>, which had been installed at some point, probably as a dependency of some other gem.

I don't know why it was trying to use the newer version, because <code>therubyracer.gemspec</code> contains <code>s.add_dependency "libv8", "~&gt; 3.3.10"</code>. And my <code>Gemfile.lock</code> says to use <code>libv8 (3.3.10.2)</code>. But alas, that is indeed what was happening.

And it's true that <code>Libv8:Module</code> does not have the method <code>include_path</code> in <code>libv8-3.11.8.13</code>, but it does in <code>libv8-3.3.10.2</code>

So that is why uninstalling all of your versions of <code>libv8</code> and then re-installing <code>therubyracer</code> works. Because all the versions of <code>libv8</code> that do not have the method <code>include_path</code> are removed completely, and the <code>libv8</code> that does have the method <code>include</code> path is reinstalled when you reinstall of <code>therubyracer</code>.

blocks|key|222766|text|考虑到如果上面的方法对我100%25有效，我想我应该把它(作为rails项目的一部分)发布出来：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|222767|gem+uninstall+libv8
bundle+update+therubyracer|code-block|syntax|javascript|222768|这确保了我得到了最新的therubyracer，以及更新版本的libV8，并且似乎修复了我遇到的多个问题，从缺少libv8.a文件到未定义的方法。|offset|length|style|CODE|222769|entityMap^0|0|0|B|C|V|5|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Considering none if the above worked for me 100%, I thought I'd post what did (as part of a rails project):

<pre><code>gem uninstall libv8
bundle update therubyracer
</code></pre>

This made sure I got the latest <code>therubyracer</code>, and also a more recent version of <code>libV8</code>, and seem to fix the multiple issues I was hitting, from missing libv8.a files, to undefined methods.

blocks|key|2879741|text|我得到了一个类似的问题，但它也抱怨找不到g%2B%2B-4.2。我确实安装了XCode命令行工具，但它正在查找/usr/bin/+g%2B%2B+-4.2，我有g%2B%2B(这是一个指向llvm-g%2B%2B-4.2的符号链接)。无论如何，我只是创建了一个指向g%2B%2B的符号链接，并再次尝试安装该包……啊，真灵!|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2879742|$++cd+/usr/bin|offset|length|style|CODE|2879743|$++sudo+ln+-s+g%2B%2B+g%2B%2B-4.2|2879744|entityMap^0|0|0|E|0|0|P|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

I got a similar issue, but it was also complaining about not finding g++-4.2. I did have XCode command line tools installed, but it was looking for /usr/bin/g++-4.2, I had g++ (which was a symbolic link pointing to llvm-g++-4.2). Anyway, I just created a symbolic link to g++ and tried the bundle install again... it worked!

<code>$ cd /usr/bin</code>

<code>$ sudo ln -s g++ g++-4.2</code>

blocks|key|228044|text|对我来说，删除Gemfile.lock文件并运行bundle+install真的很神奇。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|228045|entityMap^0|O|E|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

For me, removing the Gemfile.lock file and running <code>bundle install</code> worked it's magic.

blocks|key|228065|text|如果你需要0.11.3，但它失败了，那就试试MacOSX10.9……|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|228066|gem+uninstall+libv8
brew+install+v8
gem+install+libv8+--+--with-system-v8
gem+install+therubyracer+-v+'0.11.3'+--+--with-system-v8|code-block|syntax|javascript|228067|有关更多详细信息，请参阅this+issue。|228068|您可能不需要在最后一行使用--+--with-system-v8，但我这样做只是为了安全起见，因为当我运行命令时，我看到它开始执行Fetching:+libv8-3.11.8.17-x86_64-darwin-13.gem+(1%25)+...|228069|无论如何，当所有其他东西都不起作用的时候，它对我起作用了。|228070|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/cowboyd/therubyracer/issues/215^0|5|6|0|0|C|A|0|0|D|J|1T|1F|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|M|3|N|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1B|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

If you need <code>0.11.3</code> and it's failing give this a shot for Mac OS X 10.9...

<pre><code>gem uninstall libv8
brew install v8
gem install libv8 -- --with-system-v8
gem install therubyracer -v '0.11.3' -- --with-system-v8
</code></pre>

See <a href="https://github.com/cowboyd/therubyracer/issues/215" rel="noreferrer">this issue</a> for more details.

You probably don't need the <code>-- --with-system-v8</code> on the last line but I did it just to be safe since I saw it start doing <code>Fetching: libv8-3.11.8.17-x86_64-darwin-13.gem (1%)</code> when I ran the command...

Anyhow, it worked for me when all the other things did not.

I would appreciate some help in getting <code>gem install therubyracer</code> to work. Here is the error:

<pre><code>$ gem install therubyracer
Building native extensions. This could take a while...
ERROR: Error installing therubyracer:
 ERROR: Failed to build gem native extension.

 /Users/david/.rvm/rubies/ruby-1.9.3-p194/bin/ruby extconf.rb
checking for main() in -lobjc... yes
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.

Provided configuration options:
 --with-opt-dir
 --with-opt-include
 --without-opt-include=${opt-dir}/include
 --with-opt-lib
 --without-opt-lib=${opt-dir}/lib
 --with-make-prog
 --without-make-prog
 --srcdir=.
 --curdir
 --ruby=/Users/david/.rvm/rubies/ruby-1.9.3-p194/bin/ruby
 --with-objclib
 --without-objclib
extconf.rb:15:in `&lt;main&gt;': undefined method `include_path' for Libv8:Module (NoMethodError)
</code></pre>

Here are some notable steps that I ran before the error. They worked fine:

<pre><code>$ gem install libv8
$ brew install v8
</code></pre>

My environment is:

<ul>
<li>Mac OS X Lion 10.7.4</li>
<li>ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.4.0] (via rvm)</li>
<li>V8 version 3.9.24 (via homebrew)</li>
</ul>

`gem install therubyracer` fails on Mac OS X Lion

命令行工具

服务器

如果能帮助我让gem install therubyracer正常工作，我将不胜感激。下面是错误：$ gem install therubyracerBuilding native extensions.  This could take a while...ERROR:  Error installing theru...

问在Mac OS X Lion上` `gem install theubyracer`失败
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Mac OS X Lion上` `gem install theubyracer`失败EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Mac OS X Lion上` `gem install theubyracer`失败
EN