Wireshark · Wireshark-users: Re: [Wireshark-users] error: Neither Qt nor GTK+ 2.12 or later are available, so Wireshark can't be

[Simon K <k_simon78@xxxxxxxxx>]

---

From: Simon K <k_simon78@xxxxxxxxx>
To: Guy Harris <guy@xxxxxxxxxxxx>
Cc: "wireshark-users@xxxxxxxxxxxxx for Wireshark" <wireshark-users@xxxxxxxxxxxxx>
Sent: Friday, 28 December 2012 2:00 PM
Subject: Re: [Wireshark-users] error: Neither Qt nor GTK+ 2.12 or later are available, so Wireshark can't be compiled

---

From: Simon K <k_simon78@xxxxxxxxx>
To: Guy Harris <guy@xxxxxxxxxxxx>
Cc: "wireshark-users@xxxxxxxxxxxxx for Wireshark" <wireshark-users@xxxxxxxxxxxxx>
Sent: Friday, 28 December 2012 1:55 PM
Subject: Re: [Wireshark-users] error: Neither Qt nor GTK+ 2.12 or later are available, so Wireshark can't be compiled

Hi Harris,

Please find the attached text files .

• config.log_complete -- > Is the whole config.log file generated after running configure.

• config.log_only_error -- > Is the only error portion pasted from the config.log file

• configure_options_passed --> This file contains the options passed to the compiler and configure script

Thanks & Regards,

Lalana K

---

From: Guy Harris <guy@xxxxxxxxxxxx>
To: Simon K <k_simon78@xxxxxxxxx>
Cc: "wireshark-users@xxxxxxxxxxxxx for Wireshark" <wireshark-users@xxxxxxxxxxxxx>
Sent: Friday, 28 December 2012 12:34 PM
Subject: Re: [Wireshark-users] error: Neither Qt nor GTK+ 2.12 or later are available, so Wireshark can't be compiled

On Dec 27, 2012, at 10:41 PM, Simon K <k_simon78@xxxxxxxxx> wrote:

> # /usr/bin/pkg-config --cflags-only-I gtk+-2.0
> -I/opt/gtk2.6/include/gtk-2.0 -I/opt/gtk2.6/lib/gtk-2.0/include -I/opt/gtk2.6/include/atk-1.0 -I/opt/gtk2.6/include/pango-1.0 -I/opt/gtk2.6/include -I/opt/gtk2.6/include/freetype2 -I/opt/gtk2.6/include/glib-2.0 -I/opt/gtk2.6/lib/glib-2.0/include

OK, then the compiler should, even when run from the configure script, be looking under /opt/gtk2.6/include for the GTK+ header files.

In order to figure out why that's not happening, I'll need to see exactly what config.log is saying; just send the stuff in config.log about the compile that failed, *including* the test program and the actual compiler command, so we can see what -I flags were being passed to the compiler, as well as the error message from the compiler.

Attachment: config.log_only_error.log
Description: Binary data