On Sat, Mar 9, 2013 at 6:35 PM, Miroslaw Niegowski <[email protected]> wrote: > signal 11 suggests a hardware error and is not related to software. I would > check ram first.
Signal 11 is SIGSEGV (segmentation fault). That has nothing to do with hardware - unless you want to suggest that the MMU is involved in the process. This typically happens when dereferencing null pointers. Piotr, I'd start with simpler options - typically you do not need the sudo's for configuring and compiling. Also I'd omit the architecture unless you are cross compiling. ./configure --prefix=/usr/local/ make sudo make install Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ -- [email protected] | https://groups.google.com/d/forum/ruby-talk-google?hl=en --- You received this message because you are subscribed to the Google Groups "ruby-talk-google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
