-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
Homebrew GCC won't install on OS X 10.10 Yosemite with Xcode 6 #29845
Comments
We don't currently support either 10.10 or Xcode 6, but also note:
We would need the verbose build failure output in a gist to even diagnose this. |
Alright, I'm new to all this, I want to try to contribute however I can, Thanks for the info [: |
Is this what you need? |
I see several errors and they all appear to be just plain incompatibilities with 10.10 / Xcode 6. As is usually the case, many things are broken. I know this isn't helpful, but we don't have the resources to debug and fix problems that happen on pre-release software that most of us don't have access to. You'll have better luck reporting compilation problems to the upstream project so they can work on compatibility. Sorry :/ |
Just fyi, I've had a lot of success with this setup so far, over 100 packages without a hitch, GCC is the only package that gave me any trouble, so should be smooth sailing when you guys start to support Yosemite + Xcode 6 [: |
k, thx Jack... submitted to them and they responded quickly |
@rockymadden Yeah I noticed with other packages as well like gdb, the gnu guys are workin on a workaround but apple hasn't responded yet and unfortunately their bug reporting system isn't publicly available 👎 |
@kassafari Thanks for the information. Having never submitted a bug to Apple, I looked it up and saw that there is no transparency. I then deleted my comment realizing it was a silly question ;) Thanks for submitting those issues upstream! |
No problem, I'll post any further details here if I get any response. |
I just want to thank you for this thread, I just spent hours trying to figure this out, but I guess the only resolution is to wait. |
Hello guys ... No news or workaround ? O. |
No, not yet. For news on that, please consult the GCC issue above; there's not anything we can do. |
The gcc error is what caused all of the packages in my list here to fail the other day as well, although python3, gdk-pixbuf & gtk+ now work. (Puzzlingly). If folks need any bug reports submitted to Apple feel free to drop me a line and I'll do so & kick up a notice in the dev forums. (Not that Apple's dev forums are terribly active). |
@ohoachuck @mistydemeo There seems to be a patch now on the GCC bug tracker. I have not tried it yet, but it may be of use to people on 10.10 who need GCC now. |
I did have GCC installed previously, so, because everything wants to update it, I've pinned it, so, when I'm trying to upgrade other packages, they says gcc is pinned and won't be upgraded, but those other packages are trying to upgrade it (like cabal-install). Why those don't honor the pinning I have in place?! |
I tried copying and pasting the patch to the end of |
@AlJohri The patch seems to have been made against the trunk at the time of patch submission and not the 4.8.3 release that homebrew uses. Attempting to do so will net all sorts of fun failures:
Checking out the trunk at the time of the patch, and assuming circumventing homebrew entirely is peachy for you, the patch does work:
|
Just sharing that GCC built successfully on 10.10 DP4 for me, using the patch by James Clarke titled "Patch For GCC 4.9.1 On Yosemite". It was submitted to the upstream bug on 2014-07-2. I applied it using
and then a |
Yup. I'm privately keeping track of patched formulas that work on 10.10 over here. For various reasons, all of which are perfectly reasonable, Homebrew doesn't want to merge in patches that really belong upstream whilst Yosemite is in beta. If the problem sustains after Yosemite goes public I suspect patches will be accepted then, but until then patching one's own installation is the way to go. |
@DomT4 Yup. Even then the quickest method to get patches painlessly in Homebrew is to get them accepted upstream first 👍 |
@tobinjones Really appreciate the share! ⛵ |
I tried @tobinjones' suggestion and it just seems to hang for me for at least 2 hours. Not sure where to go from here with it. |
Have you tried this one? If you're having trouble with it hanging, invoke |
@DomT4 Worked perfectly. Thanks for that! Finally built after nearly 3 hours. Now onto the next thing that won't install... |
As @tobinjones suggested, edit the file in
then add the patch in the formula like this:
... continue with the rest of the file I never edit a install file before, and learned that you need to patch within the 'Formula'. |
I get the following after trying the patch
|
I get the following error after trying the patch above:
|
@fernandoaleman Had they same issue. I uninstalled homebrew and reinstalled.
Grab a coffee, 'cause it takes like 45mins to compile |
@mhumeSF does this work with the latest Yosemite 10.10 with Xcode Beta 6.1? |
@baldrailers Yes, I just did a successful build. |
@mhumeSF Thanks. I was able to install gcc without any issues now. |
==> ../configure --build=x86_64-apple-darwin14.0.0 --prefix=/usr/local/Cellar/gc
==> make bootstrap
make[4]: *** [multi-do] Error 1
make[3]: *** [all-multi] Error 2
make[2]: *** [all-stage1-target-libgcc] Error 2
make[1]: *** [stage1-bubble] Error 2
make: *** [bootstrap] Error 2
Error: Homebrew doesn't know what compiler versions ship with your version
of Xcode (6.0). Please
brew update
and if that doesn't help, filean issue with the output of
brew --config
:https://github.com/Homebrew/homebrew/issues
Note that we only track stable, released versions of Xcode.
Thanks!
READ THIS: https://github.com/Homebrew/homebrew/wiki/troubleshooting
These open issues may also help:
gcc: make keg-only. (#29812)
gcc 4.8.3 bottle has invalid omp.h header (#29670)
Add brew-doctor check for osx-gcc-installer (#29593)
MacOS.(gcc|clang|llvm)_version can return nil (#18781)
HOMEBREW_VERSION: 0.9.5
ORIGIN: https://github.com/Homebrew/homebrew
HEAD: 1b35e9c
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CELLAR: /usr/local/Cellar
CPU: quad-core 64-bit ivybridge
OS X: 10.10-x86_64
Xcode: 6.0 => /Applications/Xcode6-Beta.app/Contents/Developer
Clang: 6.0 build 600
X11: 2.7.6 => /opt/X11
System Ruby: 2.0.0-451
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /usr/bin/ruby
The text was updated successfully, but these errors were encountered: