-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
qt failed to build on 10.11 #40585
Comments
Qt note: to stand any hope of this being fixed you'll need to submit a patch to their Gerrit. I wouldn't even bother with a bug report at this point. |
Bye capybara? |
Moved to tracking in #40837. |
Any workarounds on this? |
None. You're welcome to report it upstream to Qt as a bug, but I wouldn't expect quick action unless someone submits a patch as well. |
I'm having the same problem when I try to install wireshark with the command: I'm also running 10.11. |
Looks like there is a patch available here: https://gitlab.com/pteam/pteam-qtbase/commit/b06304e164ba47351fa292662c1e6383c081b5ca |
Hmm, that patch is a bit outdated—won't apply as-is—but it does seem to have the right idea. |
If you submit that as a bug report, or to their code review, and get some kind of response to the issue from Qt I'm happy to consider us adding it as a patch for >= 10.11. |
The patch in http://code.qt.io/cgit/qt/qtbase.git/commit/?id=b06304e164ba47351fa292662c1e6383c081b5ca isn't outdated. It's too new: it was designed for Qt 5.2. |
@thiagomacieira Is there any chance a back port would be accepted? Qt (4) is our 65th most downloaded package and once 10.11 ships significant numbers of people will be wanting to install it on 10.11. |
No, there is none. Qt 4.8 will only receive security bugfixes and this does not qualify as such. Please keep a patch locally on homebrew instead. |
@thiagomacieira Will there be any more security patch releases of Qt 4? |
There might be. It's impossible to tell. BTW, I urge you to never build using the -qt-libxxx options in 4.8 anymore. The bundled versions are too old. Insist on and require the system versions of those libraries. |
Just FYI for those who are still coming across this issue. A simple update and upgrade now fixes the issue.
(Note: be sure to accept Xcode's agreement if you hadn't already, otherwise the upgrade fails. Once accepted then |
https://gist.github.com/eb6c70d66085fb3ce837
The text was updated successfully, but these errors were encountered: