From: Tom Cloyd <tomcloyd@...>
Date: 2009-08-28T14:37:16+09:00
Subject: Re: ruby-debug-ide for Ruby 1.9 released

Mark Moseley wrote:
> Tom Cloyd wrote:
>   
>> Confused, I am. What is the difference between ruby-debug (which won't
>> install with my ruby1.9 installation) and ruby-debug-ide (which also
>> won't install)..?
>>     
> As far as the command-line:
>   ruby-debug is for 1.8 only; ruby-debug19 is for 1.9 only
> For the IDE:
>   ruby-debug-ide is (supposed to be) for both
>   
That's helpful, in that I didn't know there was a ruby-debug19. I still 
don't know what rudy-debug-ide is, however. I have been unable to find 
anything about it via Google.

I'm very familiar with ruby-bug in ruby 1.8.7. My dependence upon it has 
been what's kept me from migrating to ruby 1.9. So, with there being a 
ruby-debug19 out, I have tried to install it. Failed. Here's the output:

$ sudo gem19 install ruby-debug19
[sudo] password for tomc:
Building native extensions.  This could take a while...
ERROR:  Error installing ruby-debug19:
        ERROR: Failed to build gem native extension.

/usr/local/bin/ruby19 extconf.rb install ruby-debug19
checking for vm_core.h... no
checking for vm_core.h... yes
checking for iseq.h... yes
checking for insns.inc... yes
checking for insns_info.inc... yes
creating Makefile

make
gcc -I. -I/usr/local/include/ruby19-1.9.1/i686-linux 
-I/usr/local/include/ruby19-1.9.1/ruby/backward 
-I/usr/local/include/ruby19-1.9.1 -I. -DHAVE_VM_CORE_H -DHAVE_ISEQ_H 
-DHAVE_INSNS_INC -DHAVE_INSNS_INFO_INC 
-I/usr/local/include/ruby19-1.9.1/ruby-1.9.1-p0 -fPIC  -O2 -g -Wall 
-Wno-parentheses  -o breakpoint.o -c breakpoint.c
gcc -I. -I/usr/local/include/ruby19-1.9.1/i686-linux 
-I/usr/local/include/ruby19-1.9.1/ruby/backward 
-I/usr/local/include/ruby19-1.9.1 -I. -DHAVE_VM_CORE_H -DHAVE_ISEQ_H 
-DHAVE_INSNS_INC -DHAVE_INSNS_INFO_INC 
-I/usr/local/include/ruby19-1.9.1/ruby-1.9.1-p0 -fPIC  -O2 -g -Wall 
-Wno-parentheses  -o ruby_debug.o -c ruby_debug.c
ruby_debug.c: In function ‘ruby_method_ptr’:
ruby_debug.c:142: error: ‘rb_method_entry_t’ undeclared (first use in 
this function)
ruby_debug.c:142: error: (Each undeclared identifier is reported only once
ruby_debug.c:142: error: for each function it appears in.)
ruby_debug.c:142: error: ‘method’ undeclared (first use in this function)
ruby_debug.c:143: warning: implicit declaration of function 
‘rb_method_entry’
ruby_debug.c: In function ‘debug_event_hook’:
ruby_debug.c:687: error: ‘rb_method_entry_t’ undeclared (first use in 
this function)
ruby_debug.c:687: error: ‘me’ undeclared (first use in this function)
make: *** [ruby_debug.o] Error 1


Gem files will remain installed in 
/usr/local/lib/ruby19/gems/1.9.1/gems/ruby-debug-base19-0.11.15 for 
inspection.
Results logged to 
/usr/local/lib/ruby19/gems/1.9.1/gems/ruby-debug-base19-0.11.15/ext/ruby_debug/gem_make.out
$
>   
>> Relative to the ruby-debug-ide install failure, here's what I get:
>>
>> $ sudo gem19 install ruby-debug-ide
>> Building native extensions.  This could take a while...
>> ERROR:  Error installing ruby-debug-ide:
>>         ERROR: Failed to build gem native extension.
>>
>>     
> Not enough info to tell. Can you zip up your entire gems directory and 
> email it to me?
>   
If I still need to do this, do you the directory's whole contents itself 
or just the dir listing?

Thanks very much for your help! I've been eagerly waiting for ruby-debug 
to work in 1.9, and I'm excited that we're pretty close to getting there.

Tom

-- 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tom Cloyd, MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< tc@tomcloyd.com >> (email)
<< TomCloyd.com >> (website) 
<< sleightmind.wordpress.com >> (mental health weblog)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~