Guy Harris
changed
bug 11367
| What |
Removed |
Added |
| Status |
UNCONFIRMED
|
INCOMPLETE
|
| Summary |
Self compiled Wireshark fails to run on MACOS
|
Self compiled Wireshark fails to run on OS X
|
| Ever confirmed |
|
1
|
Comment # 1
on bug 11367
from Guy Harris
(In reply to Jörg Mayer from comment #0)
> Created attachment 13740 [details]
> Some logs and error descriptions
>
> Build Information:
> See attached file: logs/run.log
> --
> Building Wireshark myself on Macos results in unuseable binaries:
>
> I have run macosx-setup.sh with two changes:
Neither of which involve changing the Qt version number, so is this Qt 5.5.0
that you're installing?
> 1. Comment out GTK
> 2. Install Qt5.5 to /usr/local instead of $HOME
So when the Qt installer program ran, you replaced ~/Qt or ~/Qt5.5.0 with
/usr/local in the "where should I install this?" dialog box?
> After that I run the build via the script mdoit which writes all output to
> logfiles. The script starts the newly build wireshark executable to see
> whether it works. Instead of working properly it starts and then gets stuck
> once the progress bar arrives at the right end. I need to kill wireshark (or
> force quit) for the window to disappear.
So it hangs, rather than crashing, and you get no crash report?
What gets reported if you start up Activity Monitor (in
/Applications/Utilities), select the Wireshark process, and click "Sample
Process"?
> Running the installed Wireshark also fails.
*That's* a different failure, if it's the one from installed-wireshark.log.
Try building with autotools. Qt 5.5 changed the install names for the Qt
frameworks in ways that caused a number of issues; I fixed the autotools stuff
to make it work, although those changes *might* need some more work to cope
with /usr/local installations (what's the exact path under /usr/local of the
clang_64 subdirectory of the Qt installation?), but CMake needs some separate
work for that (which involves finding out, in the CMake files, where Qt is
installed, and, in particular, finding the path of the .../clang_64/lib
directory so we can stuff it into a -Wl,-rpath,... argument).
You are receiving this mail because:
- You are watching all bug changes.