Skip to content
  1. May 18, 2013
  2. May 16, 2013
  3. May 15, 2013
  4. May 14, 2013
  5. May 12, 2013
  6. May 09, 2013
  7. May 08, 2013
  8. May 07, 2013
  9. May 06, 2013
  10. May 01, 2013
  11. Apr 26, 2013
  12. Apr 19, 2013
  13. Apr 08, 2013
  14. Apr 07, 2013
  15. Apr 06, 2013
  16. Apr 05, 2013
  17. 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
  18. Mar 31, 2013
  19. Mar 29, 2013
  20. Mar 27, 2013
  21. Mar 25, 2013
  22. Mar 21, 2013
  23. Mar 18, 2013
  24. Mar 12, 2013
  25. Feb 28, 2013