Wireshark-bugs: [Wireshark-bugs] [Bug 8494] wireshark 1.9.1 configure script should have a --wit
Guy Harris
changed
bug 8494
| What |
Removed |
Added |
| Hardware |
x86-64
|
All
|
| Summary |
wireshark 1.9.1 has automagic dependency on netlink/libnl
|
wireshark 1.9.1 configure script should have a --with-libnl option
|
Comment # 2
on bug 8494
from Guy Harris
(In reply to comment #0)
> Historically wireshark has used this feature from libpcap,
The reason why Wireshark is directly including libnl is because it wants to do
things that are currently *not* supported by libpcap (controlling the Wi-Fi
channel used by Wi-Fi adapters, and listening for indications that new
interfaces have been added or interfaces have been removed).
> given the issues with that I understand a need to change.
As per the above, it's not that Wireshark has decided to stop using some
feature from libpcap - it *still* will use the "turn on monitor mode" APIs in
libpcap, which are the reason why *libpcap* currently uses libnl (and "the
issues with that" are the reason why I *really* want to replace that libpcap
code with code that directly talks to netlink sockets rather than having to
deal with libnl1 and libnl2 and libnl3 and libnl3.1415926536... and libnl4 and
libnl5 when they come out).
> As many users don't have wifi cards
In at least once case (the "listening for indications" case), libel is being
used even if you have no Wi-Fi cards.
> (or linux machines for that matter)
If you're not building for Linux, the configure script isn't going to find
libel, and will therefore not build with libnl, so this is not an issue for
users who don't have Linux machines.
> it would be nice to have an option
> to hard disable libnl instead of having an automagic dep.
"automagic dependency" appears to be an ebuild/Gentoo term. Translating the
title into autoconfspeak, what this means is a --with-libnl option allowing the
user to specify --without-libnl if, for whatever reason, they don't want to
build with libnl on Linux (or if they're using a build system that purports to
support platforms other than Linux but can't be told "use libnl on Linux, don't
bother with it on other platforms", i.e. one that, if it supports platforms
other than Linux, doesn't do a very good job of it).
You are receiving this mail because:
- You are watching all bug changes.
