Issue #7698 has been updated by mame (Yusuke Endoh).

Status changed from Closed to Assigned
Assignee changed from kou (Kouhei Sutou) to drbrain (Eric Hodel)

Hello,

This issue seems not to be fixed completely.
"gem install rbtree" still hit this issue.
It reproduces on both trunk and 2.0.0-p0.


$ gem install rbtree
Building native extensions.  This could take a while...
ERROR:  Error installing rbtree:
        ERROR: Failed to build gem native extension.

    /home/mame/local/bin/ruby extconf.rb
checking for ruby/st.h... yes
checking for rb_exec_recursive() in ruby.h... yes
creating Makefile

make
compiling rbtree.c
compiling dict.c
linking shared-object rbtree.so

make install
/usr/bin/install -c -m 0755 rbtree.so /home/mame/local/lib/ruby/gems/2.0.0/gems/rbtree-0.3.0/.
/usr/bin/install: `rbtree.so' and `/home/mame/local/lib/ruby/gems/2.0.0/gems/rbtree-0.3.0/./rbtree.so' are the same file
make: *** [install-so] Error 1


Gem files will remain installed in /home/mame/local/lib/ruby/gems/2.0.0/gems/rbtree-0.3.0 for inspection.
Results logged to /home/mame/local/lib/ruby/gems/2.0.0/gems/rbtree-0.3.0/./gem_make.out

-- 
Yusuke Endoh <mame / tsg.ne.jp>
----------------------------------------
Bug #7698: RubyGems 2.0 has an incompatibility about installation of extension libraries
https://bugs.ruby-lang.org/issues/7698#change-36998

Author: mrkn (Kenta Murata)
Status: Assigned
Priority: High
Assignee: drbrain (Eric Hodel)
Category: lib
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2013-01-14 trunk 38812) [x86_64-linux]


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/