the command below gives this make[4]: *** [ui/qt/CMakeFiles/qtui.dir/color_utils.cpp.o] Error 1 make[4]: Leaving directory `/root/wireshark/obj-arm-linux-gnueabihf' make[3]: *** [ui/qt/CMakeFiles/qtui.dir/all] Error 2 make[3]: Leaving directory `/root/wireshark/obj-arm-linux-gnueabihf' make[2]: *** [all] Error 2 make[2]: Leaving directory `/root/wireshark/obj-arm-linux-gnueabihf' dh_auto_build: make -j1 returned exit code 2 make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/root/wireshark' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2
which seems like its related to the same error i get when i compile with a ./ configure then a make related to qreal != double on armhf everything may be different if this is done using cross compiling on something other than arm board On 5/6/2015 7:45 AM, Bálint Réczey wrote: > Could you please try: > git clean -dxf && dpkg-buildpackage -us -uc -rfakeroot > in the git directory? > The deb packages are known to build fine: > https://buildd.debian.org/status/package.php?p=wireshark&suite=unstable > > Cheers, > Balint > > 2015-05-06 16:32 GMT+02:00 wulfman <[email protected]>: >> same error after >> >> git fetch wireshark >> ./autogen.sh >> ./configure --without-qt >> >> checking whether to use /usr/local for headers and libraries... yes >> checking for sed... (cached) /bin/sed >> checking for GNU sed as first sed in PATH... yes >> checking if profile builds must be generated... no >> configure: error: Neither Qt nor GTK+ 2.12.0 or later are available, so >> Wireshark can't be compiled >> >> >> I have both versions of gtk installed if that helps >> >> http://pastebin.com/R340sZkC >> >> On 5/5/2015 10:47 PM, Guy Harris wrote: >>> On May 5, 2015, at 5:24 PM, evilwulfie <[email protected]> wrote: >>> >>>> it seems that the --without-qt option breaks the check for GTK >>> See the responses to the same messages from your other account. >>> >>> ___________________________________________________________________________ >>> Sent via: Wireshark-dev mailing list <[email protected]> >>> Archives: https://www.wireshark.org/lists/wireshark-dev >>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >>> mailto:[email protected]?subject=unsubscribe >>> >> >> -- >> The contents of this e-mail and any attachments are intended solely for the >> use of the named >> addressee(s) and may contain confidential and/or privileged information. Any >> unauthorized use, >> copying, disclosure, or distribution of the contents of this e-mail is >> strictly prohibited by >> the sender and may be unlawful. If you are not the intended recipient, >> please notify the sender >> immediately and delete this e-mail. >> >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <[email protected]> >> Archives: https://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> mailto:[email protected]?subject=unsubscribe > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:[email protected]?subject=unsubscribe > -- The contents of this e-mail and any attachments are intended solely for the use of the named addressee(s) and may contain confidential and/or privileged information. Any unauthorized use, copying, disclosure, or distribution of the contents of this e-mail is strictly prohibited by the sender and may be unlawful. If you are not the intended recipient, please notify the sender immediately and delete this e-mail. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
