Skip to content
  1. Apr 08, 2013
  2. Apr 07, 2013
  3. Apr 06, 2013
  4. Apr 05, 2013
  5. Apr 02, 2013
    • Erik Michaels-Ober's avatar
      Merge pull request #339 from gnprice/fix-shorten-workaround · a585d0b9
      Erik Michaels-Ober authored
      Fix build failure when clang installed and not used
      a585d0b9
    • Greg Price's avatar
      Better target the shorten-64-to-32 workaround (#325, #319) · 9c3e1644
      Greg Price authored
      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.
      9c3e1644
  6. Mar 31, 2013
  7. Mar 27, 2013
  8. Mar 25, 2013
  9. Mar 21, 2013
  10. Mar 18, 2013
  11. Mar 12, 2013
  12. Feb 28, 2013
  13. Feb 27, 2013
  14. Feb 26, 2013
  15. Feb 25, 2013
  16. Feb 24, 2013
  17. Feb 23, 2013
  18. Feb 22, 2013
  19. Feb 21, 2013