Had to take a day off yesterday, after my last message, about 100
messages to read, today.
I could not check (yet) with LFS7.4 - failed to build, but I had not
user, etc. for wireshark), but did with LFS7.1:
$ paco wireshark qt gtk+
gtk+-2.24.11 gtk+-3.6.4 wireshark-1.11.0
gtk+-2.24.14 qt-4.8.4 wireshark-1.8.3
(gtk+-2.24.14 installed "over" gtk+-2.24.11, same with wireshark).
Em 17-10-2013 00:27, Bruce Dubbs escreveu:
> I've just been working with wireshark-1.11.0. I can say from the build
> perspective that I'm quite disappointed. IN the previous version, the
> configure line was ./configure --prefix=/usr --sysconfdir=/etc
>
> this fails with the current version. It is trying to use both Qt5 and
> gtk+3 and both fail for me. I was able to get it to build with:
>
It configures with gtk+3. I have gtk+2 and 3, do not have qt5, only qt4.
{{{
The Wireshark package has been configured with the following options.
Build wireshark (Gtk+) : yes (with GTK+ 3)
Build wireshark-qt : yes
Build tshark : yes
Build capinfos : yes
Build editcap : yes
Build dumpcap : yes
Build mergecap : yes
Build reordercap : yes
Build text2pcap : yes
Build randpkt : yes
Build dftest : yes
Build rawshark : yes
Build echld : no
Save files as pcap-ng by default : yes
Install dumpcap with capabilities : no
Install dumpcap setuid : no
Use dumpcap group : (none)
Use plugins : yes
Use Lua library : no
Use Python binding : no
Build rtp_player : no
Build profile binaries : no
Use pcap library : yes
Use zlib library : yes
Use kerberos library : no
Use c-ares library : no
Use GNU ADNS library : no
Use SMI MIB library : no
Use GNU crypto library : yes
Use SSL crypto library : no
Use IPv6 name resolution : yes
Use gnutls library : no
Use POSIX capabilities library : no
Use GeoIP library : no
Use nl library : no
}}}
> --enable-warnings-as-errors=no --with-gtk2=yes --with-gtk3=no
>
> and also removing /opt/qt5/lib/pkgconfig from the PKG_CONFIG_PATH. In
> both cases, there are constructs that are invalid in the subject
> packages, In addition, it wants to enable-warnings-as-errors by
> default, but there are about 3600 warnings for unused-but-set-variable
> and other dead code.
I do not understand "there are constructs that are invalid in the
subject packages".
Confirmed also the warnings.
$ xzgrep unused-but-set-variable
wireshark-1.11.0-2013.10.17-07h45m22s.log.xz >
/tmp/wireshark-werrors-1.11.0-2013.10.17-07h45m22s.log
This gives me a file with 2745 lines.
>
> I also ran across an error in /usr/include/gtk-3.0/gtk/gtkwidget.h at
> line 787, as g++ seems to be confused by the spaces and it's keyword 'and'.
>
This, I cannot confirm:
$ ls wireshark-1.11.0*log*
wireshark-1.11.0-2013.10.17-07h45m22s.log.xz
wireshark-1.11.0-2013.10.17-08h10m37s.log.xz
wireshark-1.11.0-2013.10.17-08h13m54s.log.xz
$ xzgrep gtkwidget wireshark-1.11.0*log*
$
> Can someone please give wireshark-1.11.0 a try and see if the same
> issues arise?
Will try to build in LFS7.4 later.
Sent the log of LFS7.4 to your private mail (was larger than 50KB).
--
[]s,
Fernando
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
