-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
qt failed to build on 10.10 #29837
Comments
We can't really provide support for 10.10 build failures at this point. Many, many things are bound to be broken. You'll likely have better luck if you take it straight to the project developers so they can work on 10.10 compatibility. |
I have faced the same problem and had to build it from sources manually. Here is the patch:
|
Please report this to Qt; thanks! |
That warning is not relevant to the build failure and comes from Homebrew, not qt. It's simply informative to say that that version of Xcode is not yet known by Homebrew, which is normal for prerelease Xcode versions. |
Posted the bug report to qt-project: |
I managed to get around it by manually downloading: Qt libraries 4.8.6 for Mac (185 MB) (Info) from the qt-project website and install them through there. Then edit the formula you want to install (as it doesnt see that qt 4 is installed), and remove the qt dep... Other than that, I see no immediate workaround. |
The patch @anton-matosov suggested worked great, thanks |
You are welcome :) |
+1 for @anton-matosov !
Replace the line 125 (
Then change the 6th line to |
@zakelfassi Have you submitted that upstream to Qt/Digia? If not, please do so so they can fix it there. |
@zakelfassi I presume you mean line 125 instead of 122? 122 is |
@MikeMcQuaid I supposed @anton-matosov already did? I'll check. |
Thank you all! |
Please advise. |
@firedev the command you'd run is |
Oh, thanks, my bad, sorry about that. Because line started with a space I have assumed this is indentation. |
@zakelfassi For some reason, my hash is different :/ |
@imkarthikk Do you have the same version? (4.8.6) + please make sure you changed the correct line (and not used Tabs instead of spaces!) |
After success:
PS: my sha was b14afa6e4e37dba0c3b82e0fc81341665e08bc1f. |
I've rolled the qt patch into a Homebrew format, and copied the entire source code to Github to boot. Downloading from Github is so much quicker than qt. Anyway, you can grab the Yosemite patched |
I've got a few commits in Qt and I can tell you it's pretty unlikely this will be fixed unless it's submitted upstream to their Gerrit (https://codereview.qt-project.org). If someone can submit this upstream I'd be happy to help with that and we'll merge it into our formula. Thanks! |
It's going through code review here: https://codereview.qt-project.org/#/c/87515/ It looks like a different patch will be merged eventually. |
Yikes. That patch is quite a big bigger than the one liner. I'll test it out and if successful merge it into my patched qt on here later today. |
It gets merged upstream https://qt.gitorious.org/qt/qt/commits/997d626173d9aba5b01b35e4d95ad162771ba789 |
Interesting. |
Yup. Can confirm. The |
If anyone submits a pull-request I'm happy to include the patch. |
Sure. I'll draft that up tonight. |
Slight hiccups in applying that patch. The patch was built against the current Qt4 trunk by the looks of it, and consequently it doesn't apply cleanly against the stable release of Qt4. I'll probably have to manually edit the diff to account for building against the stable release over the trunk & then patch it in as a |
@DomT4 I'd also be up for just applying the relevant other commits as patches instead if it means we can use more upstream commits. |
@zakelfassi I followed your directions about changing sha1. And when I try to install qt I am getting this error; Error: SHA1 mismatch Any ideas? |
@yurci the only explanations is that 1/ you used tabs instead of spaces 2/ wrong line changed. |
You shouldn't need that; if you |
A quick&dirty patch as per Homebrew/legacy-homebrew#29837
A quick&dirty patch as per Homebrew/legacy-homebrew#29837
Same issue with --developer and --HEAD options
As a workaround, since I had already built QT under 10.9 Mavericks, I moved the old
qt
directory into/usr/local/Cellar/
and relinked like so:This appears to work. I was able to use qmake to build a rubygem that requires it.
Full report here:
https://gist.github.com/unixmonkey/9e0fc0518b0fffa43854
The text was updated successfully, but these errors were encountered: