Re: [Wireshark-dev] error: ‘qInitResources_about__init_variable__’ defined but not used [-Werror=unused-variable]
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 ;). Kind regards Gerlof Fokkema Hi, > > Do you have try with Qt5 ? > > Regards, > > On Wed, Oct 14, 2015 at 7:04 PM, Gerlof Fokkema > 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 Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] error: ‘qInitResources_about__init_variable__’ defined but not used [-Werror=unused-variable]
On Thu, Oct 15, 2015 at 10:29 AM, Gerlof Fokkema 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 > > 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 > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] error: ‘qInitResources_about__init_variable__’ defined but not used [-Werror=unused-variable]
Op do 15 okt. 2015 om 10:44 schreef Alexis La Goutte < alexis.lagou...@gmail.com>: > On Thu, Oct 15, 2015 at 10:29 AM, Gerlof Fokkema > 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 ? > After a distclean the qt5 version does build indeed. My apologies, didn't notice that these headers were automatically generated. I now have a working latest version of wireshark, now to test whether this qt version crashes less often than the GTK version :). Kind regards, Gerlof Fokkema ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Supported GnuTLS/glib/libgcrypt versions?
On 10/14/15 14:25, Peter Wu wrote: On Mon, Oct 12, 2015 at 02:02:18PM -0400, Jeff Morriss wrote: But you do raise a good point: I should start doing test compiles of the 2.0 rc on RHEL 6. I hadn't realized my users would have to continue using the Gtk+ GUI. Too bad... I have started testing with cmake + CentOS 6, it is not doing bad. At least these fixes are needed to fix the build: https://code.wireshark.org/review/10916 https://code.wireshark.org/review/11041 Funny, I actually didn't have any problems (once I updated my (customized) RPM spec file with some of the changes from master). But rpmbuild is using autotools and building from the source tarball. Speaking of bumping library versions, can we also bump the glib and libgcrypt versions? Current versions are glib 2.14 and libgcrypt 1.1.92. If we could go to glib 2.28 (Feb 2011) and gcrypt 1.5.0 (Jun 2011), it would enable us to use newer functions such as g_list_free_full. The glib change is OK for me (for RHEL 6) but it does appear to mean we'd lose support for all SLES versions; I'd tend to think that would be a bad thing. I made a mistake, SLES 12 includes glib2 2.38.2, the wiki is now updated to reflect that. For now the minimum gcrypt version is 1.4.2 (https://code.wireshark.org/review/11043). So bumping the glib version means we'd lose SLES 11. Given how recent (for an enterprise version) SLES 12 is I'd guess there are still a lot of SLES 11 users out there. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] error: ‘qInitResources_about__init_variable__’ defined but not used [-Werror=unused-variable]
On Oct 15, 2015, at 3:32 AM, Gerlof Fokkema wrote: > I now have a working latest version of wireshark, now to test whether this qt > version crashes less often than the GTK version :). You've reported those crashes on bugs.wireshark.org, right? ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Supported GnuTLS/glib/libgcrypt versions?
Den 15 okt 2015 19:43 skrev "Jeff Morriss" : > > On 10/14/15 14:25, Peter Wu wrote: >> >> On Mon, Oct 12, 2015 at 02:02:18PM -0400, Jeff Morriss wrote: >>> >>> But you do raise a good point: I should start doing test compiles of the 2.0 >>> rc on RHEL 6. I hadn't realized my users would have to continue using the >>> Gtk+ GUI. Too bad... >> >> >> I have started testing with cmake + CentOS 6, it is not doing bad. At >> least these fixes are needed to fix the build: >> https://code.wireshark.org/review/10916 >> https://code.wireshark.org/review/11041 > > > Funny, I actually didn't have any problems (once I updated my (customized) RPM spec file with some of the changes from master). But rpmbuild is using autotools and building from the source tarball. > > Speaking of bumping library versions, can we also bump the glib and libgcrypt versions? Current versions are glib 2.14 and libgcrypt 1.1.92. If we could go to glib 2.28 (Feb 2011) and gcrypt 1.5.0 (Jun 2011), it would enable us to use newer functions such as g_list_free_full. >>> >>> >>> The glib change is OK for me (for RHEL 6) but it does appear to mean we'd >>> lose support for all SLES versions; I'd tend to think that would be a bad >>> thing. >> >> >> I made a mistake, SLES 12 includes glib2 2.38.2, the wiki is now updated >> to reflect that. For now the minimum gcrypt version is 1.4.2 >> (https://code.wireshark.org/review/11043). > > > So bumping the glib version means we'd lose SLES 11. Given how recent (for an enterprise version) SLES 12 is I'd guess there are still a lot of SLES 11 users out there. > > I'm need to build on SLES11 so please don't break that. > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Supported GnuTLS/glib/libgcrypt versions?
On Oct 14, 2015, at 11:25 AM, Peter Wu wrote: > Looks like GnuTLS is only needed if you have to supply a RSA private > key. How much of it doe we use? If it's a sufficiently small amount, would it be worth just carving that part out and incorporating it directly into Wireshark, especially if that part is unlikely to change in the future in ways that we'd care about (bug fixes and new features that we'd actually use)? ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Supported GnuTLS/glib/libgcrypt versions?
On Thu, Oct 15, 2015 at 08:44:56PM +0200, Anders Broman wrote: > Den 15 okt 2015 19:43 skrev "Jeff Morriss" : > > > > On 10/14/15 14:25, Peter Wu wrote: > >> > >> On Mon, Oct 12, 2015 at 02:02:18PM -0400, Jeff Morriss wrote: > >>> > >>> But you do raise a good point: I should start doing test compiles of > the 2.0 > >>> rc on RHEL 6. I hadn't realized my users would have to continue using > the > >>> Gtk+ GUI. Too bad... > >> > >> > >> I have started testing with cmake + CentOS 6, it is not doing bad. At > >> least these fixes are needed to fix the build: > >> https://code.wireshark.org/review/10916 > >> https://code.wireshark.org/review/11041 > > > > > > Funny, I actually didn't have any problems (once I updated my > (customized) RPM spec file with some of the changes from master). But > rpmbuild is using autotools and building from the source tarball. Yes, the problems only occurred with cmake. > Speaking of bumping library versions, can we also bump the glib and > libgcrypt versions? Current versions are glib 2.14 and libgcrypt > 1.1.92. If we could go to glib 2.28 (Feb 2011) and gcrypt 1.5.0 (Jun > 2011), it would enable us to use newer functions such as > g_list_free_full. > >>> > >>> > >>> The glib change is OK for me (for RHEL 6) but it does appear to > >>> mean we'd lose support for all SLES versions; I'd tend to think > >>> that would be a bad thing. > >> > >> > >> I made a mistake, SLES 12 includes glib2 2.38.2, the wiki is now updated > >> to reflect that. For now the minimum gcrypt version is 1.4.2 > >> (https://code.wireshark.org/review/11043). > > > > > > So bumping the glib version means we'd lose SLES 11. Given how > > recent (for an enterprise version) SLES 12 is I'd guess there are > > still a lot of SLES 11 users out there. > > > > > I'm need to build on SLES11 so please don't break that. How does SLES work? Is upgrading to the latest SP seamless? How about newer releases such as SLES12? SLES11 SP2 provides gcrypt 1.5.0 which is sufficiently new, but SP1 is not compatible anymore (1.4.1 < 1.4.3). Looks like glib won't be upgraded any time soon. Do you need SSL decryption with a given RSA private key? -- Kind regards, Peter Wu https://lekensteyn.nl ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Supported GnuTLS/glib/libgcrypt versions?
On Thu, Oct 15, 2015 at 12:03:41PM -0700, Guy Harris wrote: > > On Oct 14, 2015, at 11:25 AM, Peter Wu wrote: > > > Looks like GnuTLS is only needed if you have to supply a RSA private > > key. > > How much of it doe we use? > > If it's a sufficiently small amount, would it be worth just carving > that part out and incorporating it directly into Wireshark, especially > if that part is unlikely to change in the future in ways that we'd > care about (bug fixes and new features that we'd actually use)? That was the only functionality GnuTLS is used for. The change that resulted in newer version requirement is matching the RSA private key by its public key (instead if asking the user to specify an address + port). If needed I can try to create a compatibility file for older GnuTLS versions that implements the needed functionality. -- Kind regards, Peter Wu https://lekensteyn.nl ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] error: ‘qInitResources_about__init_variable__’ defined but not used [-Werror=unused-variable]
I'm going to, and I seem to be experiencing the same (and more) problems in both the latest gtk and qt version of the git version. I'm using the 'Telephony' (and especially the 'VoIP calls' / 'RTP Player') menu of Wireshark a lot. Most of the time wireshark is great for analyzing phone calls, but especially on large files it crashes frequently (on versions ranging from 1.8 until the just now tested git version). Another bug in the latest git version I just came across is that not all VoIP calls are recognized in a file, only the first 10-20 or so are shown and then nothing. Also, I know how to code a bit of C/C++ and some basic GDB, so that's the reason I'm compiling first and asking questions/reporting bugs later :p. Kind regards, Gerlof Fokkema Op do 15 okt. 2015 om 19:56 schreef Guy Harris : > > On Oct 15, 2015, at 3:32 AM, Gerlof Fokkema > wrote: > > > I now have a working latest version of wireshark, now to test whether > this qt version crashes less often than the GTK version :). > > You've reported those crashes on bugs.wireshark.org, right? > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
