[Alexis La Goutte <alexis.lagoutte@xxxxxxxxx>]

On Thu, Oct 15, 2015 at 10:29 AM, Gerlof Fokkema <gerlof.fokkema@xxxxxxxxx> wrote:

Hello,

Yes I have, and then I get a different error:

In file included from about_dialog.cpp:25:0:
./ui_about_dialog.h:13:25: fatal error: QtGui/QAction: No such file or directory

compilation terminated.

This error is however quite logical, since the file QAction has moved from QtGui to QtWidgets in qt5.

qt4: /usr/include/qt4/QtGui/QAction

qt5: /usr/include/qt/QtWidgets/QAction

Thus this error is simply due to wireshark not being compatible with qt5 yet.

Note that replacing QtGui/QAction by QtWidgets/QAction results in a whole different set of errors, sadly it's not that simple ;).

Wireshark is compatible with qt5

you have clean the build (make distclean) after installing qt5 ? 

Kind regards

Gerlof Fokkema

Hi,

Do you have try with Qt5 ?

Regards,

On Wed, Oct 14, 2015 at 7:04 PM, Gerlof Fokkema <gerlof.fokkema@xxxxxxxxx> wrote:

Hello all,

I'm trying to compile wireshark 1.99+ from git and have a few issues while doing so.
The first issue was mentioned elsewhere on the mailing list already (removing -Wc++-compat).

The second error however I don't see mentioned anywhere and occurs only when compiling wireshark-qt:

In file included from ../../image/about.rcc.cpp:9:0:
../../image/about.rcc.cpp:1627:44: error: ‘qInitResources_about__init_variable__’ defined but not used [-Werror=unused-variable]
Q_CONSTRUCTOR_FUNCTION(QT_MANGLE_NAMESPACE(qInitResources_about))
^
/usr/include/qt4/QtCore/qglobal.h:939:21: note: in definition of macro ‘Q_CONSTRUCTOR_FUNCTION0’
static const int AFUNC ## __init_variable__ = AFUNC();
^
../../image/about.rcc.cpp:1627:1: note: in expansion of macro ‘Q_CONSTRUCTOR_FUNCTION’
Q_CONSTRUCTOR_FUNCTION(QT_MANGLE_NAMESPACE(qInitResources_about))
^
../../image/about.rcc.cpp:1627:24: note: in expansion of macro ‘QT_MANGLE_NAMESPACE’
Q_CONSTRUCTOR_FUNCTION(QT_MANGLE_NAMESPACE(qInitResources_about))

The config.log file (building most recent git version, tried 1.99.9 as well with the same result).
http://pastebin.com/sGKwiPeH

Any ideas on what causes this?

Kind regards,
Gerlof Fokkema

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe