The previous version of this logic was causing us to
pass the flag when
 * clang is on the PATH, and
 * $CC, or 'clang' if CC unset, accepts the flag.
But this is totally wrong if we have clang installed,
haven't set $CC, and are going to end up using gcc.
We end up passing the flag to gcc, which rejects it.

The real fix is to put this in the autoconf goo in MRI
upstream -- the only correct way to decide whether to pass
this flag is after we know exactly what compiler we're using
and can test if that compiler accepts the flag.  But we can
do better than before by approximating autoconf's choice of
compiler as $CC if set, 'cc' otherwise (which will typically
be a symlink to gcc or clang or another.)

Fixes: https://github.com/sstephenson/ruby-build/issues/319
  and #325, which is a dupe.

add jruby-1.7.4-dev

Keep downloaded tarball sometimes

Upgrades rubygems for 1.9.1: 1.3.5 -> 1.3.7

Ref. #290, #311

Build a shared openssl to link to Ruby as a stopgap to fix build issues some people are having, pending understanding why static linking isn't working.

fix exit status of install with verbose

bump versions to 2.1.0

$ strings ~/.rbenv/versions/2.0.0-rc2/openssl/lib/libcrypto.a |
  grep -B3 SSL_CERT_FILE
/Users/jeremy/.rbenv/versions/2.0.0-rc2/openssl/ssl/certs
/Users/jeremy/.rbenv/versions/2.0.0-rc2/openssl/ssl/cert.pem
SSL_CERT_DIR
SSL_CERT_FILE

Added a definition for 2.0.0-p0

Autoclean on unsuccessful installation

Update share/ruby-build/rbx-2.0.0-dev

Add 1.9.3-p392

Adding in JRuby 1.7.3 support

fixed typo when openssl-1.0.1e was added to ruby 2.0.0

Add -q to curl.