From 1ed6aacf5cb3265191acc61449fe68abd7c8f503 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Sun, 9 Feb 2014 08:07:02 +0000 Subject: prepare for rb_thread_blocking_region removal It'll be OK to use rb_thread_call_without_gvl when rb_thread_blocking_region is not detectable at all. We still use rb_thread_blocking_region for Ruby 2.0-2.1 because rb_thread_call_without_gvl was detectable in 1.9.3, but not usable as an internal symbol. ref: https://bugs.ruby-lang.org/issues/9502 --- ext/tdb/extconf.rb | 1 + 1 file changed, 1 insertion(+) (limited to 'ext/tdb/extconf.rb') diff --git a/ext/tdb/extconf.rb b/ext/tdb/extconf.rb index f7bb223..b309b2a 100644 --- a/ext/tdb/extconf.rb +++ b/ext/tdb/extconf.rb @@ -2,6 +2,7 @@ require 'mkmf' have_func('rb_thread_blocking_region') have_func('rb_thread_call_with_gvl') +have_func('rb_thread_call_without_gvl', 'ruby/thread.h') dir_config('tdb') have_header('tdb.h') or abort 'tdb.h missing' -- cgit v1.2.3-24-ge0c7