[
https://issues.apache.org/jira/browse/THRIFT-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118353#comment-13118353
]
Jake Farrell commented on THRIFT-1367:
--------------------------------------
I'm on os x as well. Below is the configure as well as generating the gem from
the lib/rb folder
jfarrell:rb jake$ ./configure --without-ruby
....
Building Ruby Library ........ : no
jfarrell:rb jake$ cd lib/rb
jfarrell:rb jake$ bundle
Fetching source index for http://rubygems.org/
Using rake (0.9.2)
Using cgi_multipart_eof_fix (2.5.0)
Using daemons (1.1.4)
Using fastthread (1.0.7)
Using gem_plugin (0.2.3)
Using mongrel (1.1.5)
Using rspec (1.3.2)
Using thrift (0.8.0.1) from source at
/Users/jfarrell/apache/thrift/trunk/lib/rb
Using bundler (1.0.18)
Your bundle is complete!
jfarrell:rb jake$ bundle exec rake
271 examples, 0 failures, 1 pending
gem build thrift.gemspec
Successfully built RubyGem
Name: thrift
Version: 0.8.0.1
File: thrift-0.8.0.1.gem
> Mac OSX build fails with "no such file to load -- spec/rake/spectask"
> ---------------------------------------------------------------------
>
> Key: THRIFT-1367
> URL: https://issues.apache.org/jira/browse/THRIFT-1367
> Project: Thrift
> Issue Type: Bug
> Components: Ruby - Library
> Affects Versions: 0.8
> Environment: Mac OSX 10.7.1 (Lion)
> Reporter: Peace
> Assignee: Jake Farrell
> Fix For: 0.8
>
>
> Running "make" successfully builds the compiler and most of the libs but
> fails out on the ruby lib with the message:
> Making all in rb
> /usr/bin/rake
> (in ... thrift/lib/rb)
> rake aborted!
> no such file to load -- spec/rake/spectask
> ... thrift/lib/rb/Rakefile:23
> The one hit I found online that might be related:
> https://github.com/cgs/evernote/pull/5
> "The "no such file to load -- spec/rake/spectask" error is because this gem's
> specs use rspec1.
> I just submitted a pull request to update to rspec2."
> I'm running with pkgconfig from MacPorts and starting the build from scratch
> (bootstrap.sh & onwards).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
