#54272 closed update (fixed)
wireshark2 @2.2.6_0: update to version 2.2.7
Reported by: | Schamschula (Marius Schamschula) | Owned by: | ghosthound |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch | Cc: | |
Port: | wireshark2 |
Description (last modified by ghosthound)
wireshark2 has been updated to version 2.2.7.
Note: initial build failed on wireshark.pod, could not reproduce (repeated builds all worked fine). If you encounter a build problem please open a new ticket.
Attachments (2)
Change History (9)
Changed 7 years ago by Schamschula (Marius Schamschula)
Attachment: | Portfile-wireshark2.diff added |
---|
comment:1 Changed 7 years ago by Schamschula (Marius Schamschula)
comment:2 Changed 7 years ago by ghosthound
Owner: | changed from opendarwin.org@… to ghosthound |
---|---|
Status: | new → accepted |
Yup, was working on it yesterday and ran into build errors.
comment:3 Changed 7 years ago by ghosthound
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | accepted → closed |
Resolved in 85120c45eab3efca80ee8d296f71cac579d99fad with equivalent patch.
Changed 7 years ago by Schamschula (Marius Schamschula)
Attachment: | wireshark2-main.log.gz added |
---|
comment:4 Changed 7 years ago by Schamschula (Marius Schamschula)
Unfortunately, I again ran into the same build issue: See attached log.
comment:5 Changed 7 years ago by ghosthound
Looks like there's an issue with Wireshark2 and Qt4, per this thread: https://www.wireshark.org/lists/wireshark-dev/201706/msg00013.html Options are to build with Qt5 (at least Qt 5.1) or to remove the 'setTextInteractionFlags' call from "simple_dialog.cpp". If anyone is able to give the latter a try that'd be great, otherwise I'll have a look when I can.
comment:6 Changed 7 years ago by ghosthound
See https://trac.macports.org/ticket/54276 for the build failure with Qt4.
comment:7 Changed 7 years ago by Schamschula (Marius Schamschula)
I just went the way of least resistance: I installed Qt5, and then upgraded wireshark2...
Oops. There are some build errors that need to be addressed.