[
https://issues.apache.org/jira/browse/THRIFT-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927613#action_12927613
]
Jeff Hodges edited comment on THRIFT-979 at 11/2/10 5:31 PM:
-------------------------------------------------------------
That was the deal I was trying. No clue why it doesn't seem to work.
This is what extconf.rb looks like locally:
{code}
unless RUBY_ENGINE =~ /jruby/
require 'mkmf'
$CFLAGS = "-g -O2 -Wall -Werror"
have_func("strlcpy", "string.h")
create_makefile 'thrift_native'
end
{code}
Output I get from that is the usual "Failed to build gem native extension".
This reproducible on your end?
was (Author: jmhodges):
That was the deal I was trying. No clue with it doesn't seem to work.
This is what extconf.rb looks like locally:
{code}
unless RUBY_ENGINE =~ /jruby/
require 'mkmf'
$CFLAGS = "-g -O2 -Wall -Werror"
have_func("strlcpy", "string.h")
create_makefile 'thrift_native'
end
{code}
Output I get from that is the usual "Failed to build gem native extension".
This reproducible on your end?
> ruby bindings used to work on jruby
> -----------------------------------
>
> Key: THRIFT-979
> URL: https://issues.apache.org/jira/browse/THRIFT-979
> Project: Thrift
> Issue Type: Bug
> Affects Versions: 0.5
> Reporter: Jeff Hodges
>
> The current ruby bindings do not work on JRuby do to the use of mkmf in the
> build. It used to be that on jruby, the build would just skip over the
> extconf.rb step and only install the pure ruby code. (See the current version
> up on <http://github.com/fauna/thrift>.
> I've been fighting with rubygems to figure out why I can't make this work
> like I was able to with 0.2. Unfortunately, I'm at my limit, so here's just
> the bug. Help appreciated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
