Databases
StackOverflow2013
Postsdbo
PORuby debug ide with error ubuntu
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORuby debug ide with error ubuntu
    primarykey
    data
    text
    <p>I have too many errors when i want installing ruby-debug, and ruby-debug-ide.</p> <p>Error like this (bundle install):</p> <pre><code>Using ruby_core_source (0.1.5) Using linecache19 (0.5.13) Using rails (3.2.5) Using ref (1.0.0) Installing ruby-debug-base19 (0.11.24) with native extensions Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension. /usr/local/bin/ruby extconf.rb checking for rb_method_entry_t.body in method.h... no checking for vm_core.h... no /usr/local/lib/ruby/gems/1.9.1/gems/ruby_core_source-0.1.5/lib/ruby_core_source.rb:39: Use RbConfig instead of obsolete and deprecated Config. checking for rb_method_entry_t.body in method.h... no checking for vm_core.h... yes checking for iseq.h... yes checking for insns.inc... yes checking for insns_info.inc... yes checking for eval_intern.h... yes creating Makefile make compiling breakpoint.c compiling ruby_debug.c ruby_debug.c:24:19: error: conflicting types for ‘rb_iseq_compile_with_option’ /usr/local/include/ruby-1.9.1/ruby-1.9.3-p125/vm_core.h:505:7: note: previous declaration of ‘rb_iseq_compile_with_option’ was here ruby_debug.c: In function ‘context_jump’: ruby_debug.c:2403:53: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] ruby_debug.c:2417:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] make: *** [ruby_debug.o] Error 1 Gem files will remain installed in /usr/local/lib/ruby/gems/1.9.1/gems/ruby-debug-base19-0.11.24 for inspection. Results logged to /usr/local/lib/ruby/gems/1.9.1/gems/ruby-debug-base19-0.11.24/ext/ruby_debug/gem_make.out An error occurred while installing ruby-debug-base19 (0.11.24), and Bundler cannot continue. Make sure that `gem install ruby-debug-base19 -v '0.11.24'` succeeds before bundling. </code></pre> <p>On same solution:</p> <pre><code>gem install ruby-debug-base or ruby-debug-base19 </code></pre> <p>same error,</p> <pre><code>ERROR: Failed to build gem native extension. </code></pre> <p>Does anybody know what to do?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USRichard Hutta
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PORuby debug ide with error ubuntu
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORuby debug ide with error ubuntu
      1. USmcr
      1. VTFavorite
    1. COThis seems to be the same problem: http://stackoverflow.com/questions/9122232/how-do-i-install-ruby-debug-in-ruby-1-9-3-rails-3-2-1
      singulars
      1. PORuby debug ide with error ubuntu
      1. USFrost
    2. COYes, i read this, but still doing this ERROR: Failed to build gem native extension.
      singulars
      1. PORuby debug ide with error ubuntu
      1. USRichard Hutta
    3. COI heard ruby-debug19 is deprecated, you should use the debugger gem instead...
      singulars
      1. PORuby debug ide with error ubuntu
      1. UScitraL
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload