I wonder if you all build using clang?
I use gcc6 (qt5 version 5.7.0, all installed using home brew), and get the
below compilation issue on Sierra (and likely since my recent upgrade to
Sierra).
Any ideas?
Thanks!
cd /Users/itisntme6/data/wireshark/wireshark/build/wsutil &&
/usr/local/opt/gcc/bin/gcc-6 -DG_DISABLE_DEPRECATED
-DG_DISABLE_SINGLE_INCLUDES -DWS_BUILD_DLL -Dwsutil_EXPORTS
-I/Users/itisntme6/data/wireshark/wireshark/build
-I/Users/itisntme6/data/wireshark/wireshark
-I/Users/itisntme6/data/wireshark/wireshark/epan
-I/Users/itisntme6/data/wireshark/wireshark/tools/lemon -isystem
/usr/local/opt/gettext/include -I/usr/local/opt/qt5/include -isystem
/usr/local/include -isystem /usr/local/Cellar/geoip/1.6.9/include -isystem
/usr/local/Cellar/glib/2.50.2/include/glib-2.0 -isystem
/usr/local/Cellar/glib/2.50.2/lib/glib-2.0/include -isystem
/usr/local/Cellar/pcre/8.39/include -isystem
/usr/local/Cellar/gnutls/3.4.17/include -isystem
/System/Library/Frameworks/Kerberos.framework/Headers -isystem
/usr/local/opt/lua/include -iframework /usr/local/opt/qt5/lib -isystem
/usr/local/opt/qt5/lib/QtCore.framework/Headers -isystem
/usr/local/opt/qt5/./mkspecs/macx-clang -isystem
/usr/local/opt/qt5/lib/QtMacExtras.framework/Headers -isystem
/usr/local/opt/qt5/lib/QtGui.framework/Headers -isystem
/System/Library/Frameworks/OpenGL.framework/Headers -isystem
/usr/local/opt/qt5/lib/QtMultimedia.framework/Headers -isystem
/usr/local/opt/qt5/lib/QtNetwork.framework/Headers -isystem
/usr/local/opt/qt5/lib/QtPrintSupport.framework/Headers -isystem
/usr/local/opt/qt5/lib/QtWidgets.framework/Headers -isystem
/usr/local/opt/qt5/lib/QtSvg.framework/Headers -fexcess-precision=fast
-Wno-unused-parameter -Wno-unused-function -Wno-deprecated-declarations
-fvisibility=hidden -O2 -g -DNDEBUG -fPIC -Wall -Wextra -Wendif-labels
-Wpointer-arith -Wformat-security -fwrapv -fno-strict-overflow -Wvla
-Waddress -Wattributes -Wdiv-by-zero -Wignored-qualifiers -Wpragmas
-Wno-overlength-strings -Wno-long-long -Wno-unused-parameter -Wc++-compat
-Wshadow -Wno-pointer-sign -Wold-style-definition -Wstrict-prototypes
-Wlogical-op -Wjump-misses-init -Wunused-const-variable -Werror=implicit
-std=gnu99 -Werror -o CMakeFiles/wsutil.dir/airpdcap_wep.c.o -c
/Users/itisntme6/data/wireshark/wireshark/wsutil/airpdcap_wep.c
/System/Library/Frameworks/CoreFoundation.framework/Headers/CFURL.h:777:39:
error: 'deprecated' undeclared here (not in a function)
const CFStringRef kCFURLLabelColorKey API_DEPRECATED("Use
NSURLLabelColorKey", macosx(10.6, 10.12), ios(4.0, 10.0), watchos(2.0,
3.0), tvos(9.0, 10.0));
^
/System/Library/Frameworks/CoreFoundation.framework/Headers/CFURL.h:777:39:
error: 'message' undeclared here (not in a function)
const CFStringRef kCFURLLabelColorKey API_DEPRECATED("Use
NSURLLabelColorKey", macosx(10.6, 10.12), ios(4.0, 10.0), watchos(2.0,
3.0), tvos(9.0, 10.0));
^
On Fri, Oct 21, 2016 at 8:34 PM, Francisco Javier Sanchez-Roselly <
franciscojavier.sanchezrose...@ujaen.es> wrote:
> hi Jaap,
>
> On 21 Oct 2016, at 14:28, Jaap Keuter <jaap.keu...@xs4all.nl> wrote:
>
> Hi Francisco,
>
> That looks to me that the Wireshark splash image isn’t properly packed.
> There are two version of it, one standard (called wssplash.png) which is
> used in the released versions, and one development (called
> wssplash_dev.png) which is used in the development versions. Somehow the
> applicable graphic is not available. Someone with knowledge of the
> macOS packaging might have a clue.
>
>
> the issue comes out working on Wireshark version available on git -the
> development one-. i guess it is not a particular OS X problem. may be one
> currently builds GTK interface version.
>
> In the mean time, this shouldn’t really hold you back improving your
> change, as it can be reviewed/tested in Wireshark (Qt). Are you still
> pursuing this?
>
>
> i was also trying Qt through MacPorts, but i was unlucky too. so now i
> have Qt version available in qt.io an i am currently amending the
> dissector issues.
>
> thanks, regards.
>
> Thanks,
> Jaap
>
>
>
> On 20 Oct 2016, at 20:17, Francisco Javier Sanchez-Roselly <franciscojavi
> er.sanchezrose...@ujaen.es> wrote:
>
> hi Me (All):
>
> On 13 Oct 2016, at 22:49, Francisco Javier Sanchez-Roselly <franciscojavi
> er.sanchezrose...@ujaen.es> wrote:
>
> hi All,
>
> i have been following the thread as it was impossible for me to install
> Wireshark from the sources in Sierra -the previous El Capitan installation
> worked nicely-.
>
> i have tried the steps described in README.macos, afterwards i have
> installed the ‘required' ports but my install hangs because of an error on
> ‘uic-qt5’. finally i did configure successfully disabling qt, but
> wireshark-gtk stops because of a missed image file.
>
>
> after a week and several compilations on OS X Sierra, i can asses
> wireshark-gtk execution hangs on this error:
>
> (process:90095): GLib-GObject-WARNING **: gsignal.c:2475: signal `realize'
> is invalid for instance `0x7fc36b00f060' of type `(null)'
> **
> ERROR:gui_utils.c:2076:GdkPixbuf *ws_gdk_pixbuf_new_from_resource(const
> char *): assertion failed (err == NULL): El recurso en
> «/org/wireshark/image/wssplash_dev.png» no existe ((null), 0)
> Abort trap: 6
>
> you can build and run using Qt from qt.io -impossible for me using
> MacPorts-.
>
> regards.
>
> i please ask for any guidance on my journey. sorry if my problem is a
> trivial one.
>
> thanks, regards.
>
> pd.- i can post the specific errors if required.
>
> On 12 Oct 2016, at 22:08, Graham Bloice <graham.blo...@trihedral.com>
> wrote:
>
>
>
> On 12 October 2016 at 20:15, Evan Huus <eapa...@gmail.com> wrote:
> On Wed, Oct 12, 2016 at 3:04 PM, Guy Harris <g...@alum.mit.edu> wrote:
>
> On Oct 12, 2016, at 11:41 AM, Jeff Morriss <jeff.morriss...@gmail.com>
> wrote:
>
> Just for fun I did a quick search for that Usage output (minus the
> "Wireshark" prefix which is clearly $0) and found this program which has
> that exact output:
>
> https://github.com/the-tcpdump-group/libpcap/blob/
> master/tests/capturetest.c
>
>
> Yeah, that's one of a pile of test programs I wrote to test various
> libpcap features.
>
> The binary is *not* part of a libpcap installation, so there shouldn't be
> an executable for it unless the test programs were built.
>
> Evan, what happens if you remove the build directory entirely, re-create
> it, do a cmake in it, and then redo the build?
>
>
> Completely blowing away the build directory and starting again seems
> to have fixed it. That was really weird, especially since (to my
> knowledge) I don't even have a source build of libpcap on this
> machine.
>
> Anywho, thanks everyone for the help!
>
>
> CMake standard repair #1 :-)
>
> --
> Graham Bloice
>
>
> ____________________________________________________________
> _______________
> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> <wireshark-dev-requ...@wireshark.org?subject=unsubscribe>
>
>
>
>
>
> ____________________________________________________________
> _______________
> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=
> unsubscribe
>
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
