From b6ec1891ec6280c186e78ec77b88e6934ca7d653 Mon Sep 17 00:00:00 2001 From: Pat Allan Date: Sun, 21 May 2017 05:33:35 +0000 Subject: Update respond_to? calls for second argument. Rack (since v2) has started explicitly listing the second (optional) argument for respond_to?, which matches the underlying Ruby spec. This patch fixes the calls in both C and Ruby approaches. [ew: add test, use rb_obj_respond_to if available] --- ext/clogger_ext/extconf.rb | 1 + 1 file changed, 1 insertion(+) (limited to 'ext/clogger_ext/extconf.rb') diff --git a/ext/clogger_ext/extconf.rb b/ext/clogger_ext/extconf.rb index 523b314..b2c0891 100644 --- a/ext/clogger_ext/extconf.rb +++ b/ext/clogger_ext/extconf.rb @@ -22,6 +22,7 @@ begin have_func('rb_thread_call_without_gvl', 'ruby/thread.h') have_func('rb_thread_blocking_region', 'ruby.h') have_func('rb_thread_io_blocking_region', 'ruby.h') + have_func('rb_obj_respond_to', 'ruby/intern.h') create_makefile('clogger_ext') rescue Object => err warn "E: #{err.inspect}" -- cgit v1.2.3-24-ge0c7