Wireshark-bugs: [Wireshark-bugs] [Bug 13011] New: Header inclusion missing in dissector packet-r

Date: Wed, 12 Oct 2016 16:51:17 +0000
Bug ID 13011
Summary Header inclusion missing in dissector packet-rlc-lte
Product Wireshark
Version 2.2.1
Hardware x86
OS Linux (other)
Status UNCONFIRMED
Severity Normal
Priority Low
Component Build process
Assignee [email protected]
Reporter [email protected]

Build Information:
TShark (Wireshark) 2.3.0 (v2.3.0rc0-993-g53c20dd from master)

Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with libpcap, without POSIX capabilities, without libnl, with
GLib 2.42.2, with zlib 1.2.7, without SMI, without c-ares, without Lua, without
GnuTLS, without Gcrypt, without Kerberos, without GeoIP.

Running on Linux 3.10.0-327.13.1.el7.x86_64, with        Intel(R) Xeon(R) CPU
E5-2440 0 @ 2.40GHz (with SSE4.2), with 3624 MB of physical memory, with locale
en_US.UTF-8, with libpcap version 1.5.3, with zlib 1.2.7.

--
Hello,

When trying to work with file given on:

https://wiki.wireshark.org/RLC-LTE

i.e. https://www.wireshark.org/~martinm/rlc_lte_logger.c

and compiling using (gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4))

gcc rlc_lte_logger.c `pkg-config --cflags --libs glib-2.0 wireshark` -o main
-DHAVE_STDARG_H

I get an error:

In file included from rlc_lte_logger.c:48:0:
/usr/include/glib-2.0/../wireshark/epan/dissectors/packet-rlc-lte.h:78:5:
error: unknown type name ‘nstime_t’
     nstime_t        time;

After adding:
#include "../wireshark/epan/packet_info.h"

in /usr/include/glib-2.0/../wireshark/epan/dissectors/packet-rlc-lte.h

things work fine. I also, noticed the same problem with some other files. This
is missing from the github pages too. I'm guessing it's some configuration
issue during installation. Am I missing something or do we have a bug?


You are receiving this mail because:
  • You are watching all bug changes.