Issue #7698 has been updated by nagachika (Tomoyuki Chikanaga).


Hello,

The following is the output of gem install rbtree on my environment (ruby 2.1.0dev (2013-06-16 trunk 41337) [x86_64-darwin10.8.0])
It seems that rbtree need to catch up with constify of RBasic::klass and RHash::ifnone for RGenGC.
ko1, what do you think? Is it intended incompatibility?

% gem install rbtree
Fetching: rbtree-0.4.1.gem (100%)
Building native extensions.  This could take a while...
ERROR:  Error installing rbtree:
        ERROR: Failed to build gem native extension.

    /Users/nagachika/opt/ruby-trunk/bin/ruby-trunk extconf.rb
checking for ruby/st.h... yes
checking for rb_exec_recursive() in ruby.h... yes
checking for rb_exec_recursive_paired() in ruby.h... yes
checking for rb_proc_lambda_p() in ruby.h... yes
creating Makefile

make
compiling dict.c
compiling rbtree.c
rbtree.c: In function ???copy_dict???:
rbtree.c:755: error: assignment of read-only member ???klass???
rbtree.c: In function ???rbtree_to_hash???:
rbtree.c:1292: error: assignment of read-only member ???ifnone???
make: *** [rbtree.o] Error 1

----------------------------------------
Bug #7698: RubyGems 2.0 has an incompatibility about installation of extension libraries
https://bugs.ruby-lang.org/issues/7698#change-39973

Author: mrkn (Kenta Murata)
Status: Closed
Priority: High
Assignee: nobu (Nobuyoshi Nakada)
Category: lib
Target version: current: 2.1.0
ruby -v: ruby 2.0.0dev (2013-01-14 trunk 38812) [x86_64-linux]
Backport: 


The current rubygem included in ruby-head has an incompatibility about installation of extension libraries.
This incompatibility makes `make install` to be failed because the current gem doesn't separate build, source and install directories.

This is reported as a bug of bigdecimal's gemspec in #7344 firstly, but Tadashi Saito pointed out it also can be reproduced in other gems including extension libraries, such as decimal.gem.
I think this incompatibility will make gem-developers to be in trouble after ruby-2.0 is released.
So this should be resolved before ruby-2.0 is released.



-- 
http://bugs.ruby-lang.org/