On Jul 23, 2015, at 5:57 PM, Luke Mewburn wrote:
> I appreciate the intention of such setup scripts. Generally I haven't
> needed them (until now!). I'm a little leery of stuff that's going to
> potentially fiddle with my /usr
It shouldn't be doing anything to /usr other than /usr/local unless
On Thu, Jul 23, 2015 at 02:45:57PM -0700, Guy Harris wrote:
|
| On Jul 22, 2015, at 8:20 PM, Luke Mewburn wrote:
|
| > I suspect that this Qt bug (QTBUG-34160) may not be easily worked-around
| > within Wireshark without radical menu reorganisation.
|
| I'm not sure how radical
On Jul 22, 2015, at 8:20 PM, Luke Mewburn wrote:
> I suspect that this Qt bug (QTBUG-34160) may not be easily worked-around
> within Wireshark without radical menu reorganisation.
I'm not sure how radical
https://code.wireshark.org/review/#/c/9760/
is, but do the issues from bug 10890
On Tue, Jul 21, 2015 at 09:26:42PM -0700, Guy Harris wrote:
|
| On Jul 21, 2015, at 7:53 PM, Luke Mewburn wrote:
|
| > I've been experiencing weird issues running my Mac OS X builds of
| > wireshark compiled with Qt 5.2 from Homebrew.
Correcting myself: the Homebrew version is Qt 5.4.
On Jul 21, 2015, at 7:53 PM, Luke Mewburn wrote:
> I've been experiencing weird issues running my Mac OS X builds of wireshark
> compiled with Qt 5.2 from Homebrew.
How does it work when compiled with Qt 5.3.2 or 5.5.0 from qt.io? (5.5.0 won't
work if you're using Snow Leopard.)
Hi,
I've been experiencing weird issues running my Mac OS X builds of wireshark
compiled with Qt 5.2 from Homebrew.
I've configured wireshark with:
configure --disable-gtktest --with-qt --with-gnutls
--without-geoip --disable-warnings-as-errors --no-create
