“gem install ruby-debug-ide” now works for both Ruby 1.8 and 1.9
(version 0.4.7).
Mark M. wrote:
“gem install ruby-debug-ide” now works for both Ruby 1.8 and 1.9
(version 0.4.7).
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)…?
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.
/usr/local/bin/ruby19 extconf.rb install ruby-debug-ide
Building native extensions. This could take a while…
Building native extensions. This could take a while…
Gem files will remain installed in
/usr/local/lib/ruby19/gems/1.9.1/gems/ruby-debug-ide-0.4.7 for
inspection.
Results logged to
/usr/local/lib/ruby19/gems/1.9.1/gems/ruby-debug-ide-0.4.7/ext/gem_make.out
tomc@tomc-desktop:~/Ruby-work/setnet/bin$
That gem_make.out file contains…
/usr/local/bin/ruby19 extconf.rb install ruby-debug-ide
Building native extensions. This could take a while…
Building native extensions. This could take a while…
Any help in making sense of this would be much appreciated.
t.
–
Tom C., MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
Tom C. 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
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?
Tom C. wrote:
don’t know what rudy-debug-ide is, however. I have been unable to find
anything about it via Google.
ruby-debug-ide is two things:
1.) a standardized communication protocol between Ruby implementations
(or more precisely Ruby debuggers) and Ruby IDEs. Every debugger that
conforms to the protocol will automatically work with every Ruby IDE
that conforms to the protocol and vice versa.
2.) a set of gems that implement adapters for said standardized
protocol for debuggers that are not compliant with the protocol,
like ruby-debug for example.
To put it another way: ruby-debug-ide is to debuggers and IDEs as Rack
is to web frameworks and web servers.
jwm
Mark M. wrote:
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
$
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 C., MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
Tom C. wrote:
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.
This is the result of a bug in ruby-debug-base19; it doesn’t work
properly with ruby-1.9.1-p0. I recommend updating the Ruby 1.9 version
to ruby-1.9.1-p243 or ruby-1.9.2-preview1.
But in case you or someone else has to stay with 1.9.1-p0, I will fix
this and release an update later today.
Jörg W Mittag wrote:
As far as the command-line:
is to web frameworks and web servers.
jwm
Great - I get it now. I rather suspected that might be what it was
about, but was quite unsure.
t.
–
Tom C., MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
New gem is up now; ruby-debug-base19 v0.11.16.
Mark M. wrote:
$ sudo gem19 install ruby-debug19
But in case you or someone else has to stay with 1.9.1-p0, I will fix
this and release an update later today.
Wow, what a difference a day makes! Thanks, Mark, for your work, and
your help. I’ve successfully installed ruby-debug19. And I’ll look into
updating my ruby 1.9 version, as well.
Thanks. I’ve waited a while for real access to ruby 1.9, since I had to
have ruby-debug.
t.
–
Tom C., MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)