Comment # 12
on bug 10876
from Guy Harris
(In reply to Steven Swor from comment #9)
> (In reply to João Valverde from comment #7)
> > (In reply to Steven Swor from comment #4)
> > > Created attachment 14569 [details]
> > > config.log for --enable-wireshark=no --disable-glibtest on centos7
> > >
> > > I'm running into the same issue with RHEL7.2. I've been able to reproduce it
> > > with an official centos7 docker image.
> > >
> > > Attached is the config.log for running `./configure --enable-wireshark=no
> > > --disable-glibtest`.
> >
> > yum install -y glib2-devel
>
> Thanks, João. After installing glib2-devel I'm able to build.
>
> Would this be considered a workaround? If I use `--enable-wireshark=no` and
> `--enable-glibtest=no`, shouldn't that eliminate the glib dependency
> entirely?
The only way to eliminate a dependency on GLib would be to take *all* of the
code in:
libwiretap;
libwireshark;
libwsutil;
tshark and all the other command-line utilities;
the Qt version of Wireshark;
all the other libraries;
that uses GLib routines and change it not to use GLib routines.
Otherwise, Wireshark *requires* Glib, *even if you're not building the GUI
version of Wireshark*.
Is there any reason the inability of anything in the Wireshark source
distribution to be built without GLib should be treated as anything other than
a not-likely-to-be-implemented-anytime-in-the-near-future enhancement request
(i.e. as a request to get rid of all the non-GTK+ code that uses GLib)?
You are receiving this mail because:
- You are watching all bug changes.
