Update a String#{to_sym,intern} spec for "+,-"

Follow ticket-9048
See below links

* http://bugs.ruby-lang.org/issues/9048
* https://github.com/ruby/ruby/pull/383#issuecomment-26915103
Improve some special operators specs
Remove outdated special operators
Add rb_class_real per #2358
debian stable package support for rubinis-2.2.

File necessary to build a .deb package for Debian Stable(wheezy).

Rubinius 2.2.6+ or MRI 1.8/1.9 can be used to build the package. There were
changes in Rubinius prior to 2.2.4 to make this work.

Conflict & Replace MRI ruby packages.

gem is a separate alternatives command in rubygems1.8. This is broken. The gem
command is include in ruby1.9.1 package and in rubinius it is also included.
The gem command must switch in lock step with the ruby command otherwise
everything breaks.

I force package conflict until the MRI packages are fixed.

dpkg-buildflags is used for the default build flags. This fixes some common
problems and allows system specific configuration.

Description in control file by @brixen
"Rewrote the description as one paragraph to meet the formatting restrictions.
I focused on more direct technical language as I expect the audience for the
description to be knowledgable about Ruby, programming, or the technology
described generally."
Fix handling of non ASCII values on ENV

If we set an environment variable with a non ASCII value and we set
Encoding.default_internal the program can crash.

Checking for ASCII values before we proceed to encode solves the
problem.

I don't like using a conditional in the spec, but if we are going to use
the env set by the user while running the spec suite we need to ignore
some of the values.
Set RBX_PREFIX_PATH to the build prefix when building extensions

When building rbx with the same path settings as an already-
installed rbx, it now uses the former and not the latter to build
the gems.

Important to have for packaging.
Merge pull request #3008 from heftig/master

Set RBX_PREFIX_PATH to the build prefix when building extensions
Use stricter type checks to prevent potential null pointer dereferences
Finish collection cycle for non concurrent gc

This would mean we wouldn't do the sweeping and mark rotation, causing
bugs like mentioned in #2995 where we would crash with the
non-concurrent GC.
Delete GC data when not running concurrent GC
Fix Immix debugging logic
Don't scan C data structures during concurrent GC

This prevents walking C data structures concurrently, which might be in
the middle of free'ing data or other non thread safe operations.
Make the Gems cache directory configurable.

This directory can be set using the --gems-cache option when configuring
Rubinius. Using this option one can move the Gems cache directory out of the
local working tree if needed. This in turn means CI systems that wipe the local
working tree don't have to constantly re-download the same Gems.

Considering this in itself takes time and RubyGems doesn't always respond this
can save quite the time in a build process. The trade off is that you'll have
to, once in a while, prune this directory to prevent it from ever growing in
size.

Corresponding issue: #3011
Removed an extra space.

This somehow sneaked in. I swear this never happens to me.
Ensure readline/readline.h is available during the configure process
Merge pull request #3009 from skottler/feature/check_missing_pkgs

Ensure readline/readline.h is available during the configure process
Don't leak FORTIFY_SOURCE from LLVM.

When running a debug build llvm-config could potentially leak _FORTIFY_SOURCE
in to the list of CFLAGS. This in turn would break debug builds due to warnings
being treated as errors.

This particular case is platform dependant. For example, it occurs on Amazon
CentOS but not on my local Arch Linux installation. Linux distributions keep
surprising me, and not always in good ways sadly.
Merge branch 'master' of github.com:rubinius/rubinius
Include stdio.h when checking for headers.

The header readline/readline.h, and potentially millions of others, have an
implicit dependency on this header. Not including this header would result in a
header check failure.