Comment # 17
on bug 10876
from João Valverde
(In reply to Michael Davey from comment #15)
> >> If glib is still required to build the various non-gut components
>
> > It is. We make significant use of its functions in a number of places.
>
> Yes, that is my confusion.
>
> If --disable-glibtest and --enable-glibtest=no don't actually disable the
> test (on the basis that glib is always needed and presumably the argument
> being that therefore the test should always be executed), then these flags
> should be obsoleted and the documentation updated accordingly.
The --disable-glibtest flag does work on Wireshark 1.12.
What happens is, in the case of a broken Glib installation, which the macro
assumes instead of a missing installation (because AM_PATH_GLIB_2_0 is part of
Glib), it tries to be helpful and figure out what went wrong and that's what
you're seeing here.
You are receiving this mail because:
- You are watching all bug changes.