3 ms·

GCC is essentially broken, rendering compilation of standard packages impossible. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61407 https://gcc.gnu.org/bugzil

by randall 12y ago

GCC is essentially broken, rendering compilation of standard packages impossible. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61407 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61407 Our team was on Yosemite but we all had to move back to Mavericks to actually do work.

nailer 12y ago
brew (which I'd consider on OS X to be `standard packages`) generally uses LLVM rather than GCC, and has been fine throughout 10.10
- randall 12y ago
  Correct... but many ruby gems and node.js modules compile using gcc. (v8 being the most annoying one for us)
  - anders 12y ago
    are you sure it's actually gcc and not clang, because "gcc" on OS X is clang
    - randall 12y ago
      It's doing gcc 4.2, and when you try to install / compile a higher version it fails. Pretty sure.
  - _frog 12y ago
    I've had luck installing most Ruby gems used by my projects. The only exception so far has been Nokogiri, and even in that case there were instructions on the project's web page that got it to install without a hitch.
- hashtree 12y ago
  As you mentioned, there are still a handful that currently have GCC issues, namely Haskell (GHC) and MongoDB. https://github.com/Homebrew/homebrew/issues/29845 https://github.com/Homebrew/homebrew/issues/29845