#60123 closed defect (fixed)
quassel, quassel-client @0.13.1_1: error: use of overloaded operator '<<' is ambiguous
Reported by: | rseichter (Ralph Seichter) | Owned by: | landonf (Landon Fuller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.2 |
Keywords: | Cc: | Tatsh (Andrew Udvare) | |
Port: | quassel, quassel-client |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Building quassel-client fails with the following error message. See also attached log.
/opt/local/libexec/qt5/lib/QtCore.framework/Headers/qmetatype.h:818:16: error: use of overloaded operator '<<' is ambiguous (with operand types 'QDataStream' and 'const DccConfig::IpDetectionMode')
Attachments (1)
Change History (6)
Changed 5 years ago by rseichter (Ralph Seichter)
comment:1 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Port: | @0.13.1_1 removed |
Summary: | quassel-client: error: use of overloaded operator '<<' is ambiguous → quassel-client @0.13.1_1: error: use of overloaded operator '<<' is ambiguous |
comment:2 Changed 4 years ago by Tatsh (Andrew Udvare)
Cc: | Tatsh added |
---|
comment:3 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Port: | quassel added |
---|---|
Summary: | quassel-client @0.13.1_1: error: use of overloaded operator '<<' is ambiguous → quassel, quassel-client @0.13.1_1: error: use of overloaded operator '<<' is ambiguous |
comment:4 Changed 4 years ago by landonf (Landon Fuller)
Owner: | set to landonf |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:5 Changed 4 years ago by rseichter (Ralph Seichter)
Thank you for this, Landon. In combination with my Pulseaudio fix for https://trac.macports.org/ticket/61107 , I now finally have a working Quassel client on my MacBook Pro.
Note: See
TracTickets for help on using
tickets.
I see the same problem when building quassel or quassel-client from source. However we have binaries of this version of quassel and quassel-client, so we were able to build them at some point in the past. What changed? Since the error is coming from a Qt file, I'm guessing Qt got updated.
Looking further, I find that quassel is indeed incompatible with Qt 5.14 per this upstream bug report: https://bugs.quassel-irc.org/issues/1544
And this pull request to fix it: https://github.com/quassel/quassel/pull/518
I tried applying that patch to 0.13.1, unfortunately it's a large patch and most of it fails to apply. I don't really want to invest a lot of time backporting the fix when the correct fix is for the developers to release a new version. As of 10 days ago, they said a 0.14-rc1 would be released in a few weeks. So if you want this fixed, please gently nudge the developers of quassel toward releasing 0.14. Then we can update to that version in MacPorts.