<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: libpcap (for tcpdump) compile in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999712#M542097</link>
    <description>Sounded like a good idea, got the source for libpcap 0.9.4 from tcpdump.org.  It still tried to use flex and bison, so did configure --without-flex.&lt;BR /&gt;&lt;BR /&gt;It said our LEX wasn't sufficient ??&lt;BR /&gt;&lt;BR /&gt;Got:&lt;BR /&gt;&lt;BR /&gt;configure: WARNING: don't have both flex and bison; reverting to lex/yacc&lt;BR /&gt;checking for capable lex... insufficient&lt;BR /&gt;configure: error: Your operating system's lex is insufficient to compile&lt;BR /&gt; libpcap.  flex is a lex replacement that has many advantages, including&lt;BR /&gt; being able to compile libpcap.  For more information, see&lt;BR /&gt; &lt;A href="http://www.gnu.org/software/flex/flex.html" target="_blank"&gt;http://www.gnu.org/software/flex/flex.html&lt;/A&gt; .</description>
    <pubDate>Mon, 28 Aug 2006 14:09:29 GMT</pubDate>
    <dc:creator>Lynne Seamans</dc:creator>
    <dc:date>2006-08-28T14:09:29Z</dc:date>
    <item>
      <title>libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999710#M542095</link>
      <description>&lt;!--!*#--&gt;We still have an 11.00 system due to application restrictions.&lt;BR /&gt;&lt;BR /&gt;I'd like to get tcpdump on it, so i need libpcap.  There is no depot for either on 11.00, so i'm trying to compile the code i downloaded from the porting centre:&lt;BR /&gt;&lt;A href="http://hpux.connect.org.uk/hppd/hpux/Networking/Admin/libpcap-0.9.4/" target="_blank"&gt;http://hpux.connect.org.uk/hppd/hpux/Networking/Admin/libpcap-0.9.4/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;libpcap requires flex, bison, gcc and make.  Got 'em all, although maybe not the latest.&lt;BR /&gt;&lt;BR /&gt;configure runs, go to "gmake" (per instructions) -- it completes some lines, then dies with a pipe error:&lt;BR /&gt;&lt;BR /&gt;(removed lines)&lt;BR /&gt;$$.scanner.c scanner.c&lt;BR /&gt;bison -y -p pcap_ -d grammar.y&lt;BR /&gt;gmake: *** [grammar.c] Broken pipe&lt;BR /&gt;&lt;BR /&gt;Very similar with regular "make", gets a "Termination Signal 13", which is a sigpipe, so i guess they're saying the same thing.&lt;BR /&gt;&lt;BR /&gt;Anybody have success with this?</description>
      <pubDate>Fri, 25 Aug 2006 15:01:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999710#M542095</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2006-08-25T15:01:52Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999711#M542096</link>
      <description>If you get libpcap sources from &lt;A href="http://www.tcpdump.org" target="_blank"&gt;www.tcpdump.org&lt;/A&gt; you can compile them just fine with the HP compiler.  No real need for gmake, flex or bison.&lt;BR /&gt;&lt;BR /&gt;I've never tried with those, and gcc under HP-UX.  Just the HP compiler (unbundled) and the HP-UX standard make lex and yacc.</description>
      <pubDate>Fri, 25 Aug 2006 19:34:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999711#M542096</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-08-25T19:34:28Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999712#M542097</link>
      <description>Sounded like a good idea, got the source for libpcap 0.9.4 from tcpdump.org.  It still tried to use flex and bison, so did configure --without-flex.&lt;BR /&gt;&lt;BR /&gt;It said our LEX wasn't sufficient ??&lt;BR /&gt;&lt;BR /&gt;Got:&lt;BR /&gt;&lt;BR /&gt;configure: WARNING: don't have both flex and bison; reverting to lex/yacc&lt;BR /&gt;checking for capable lex... insufficient&lt;BR /&gt;configure: error: Your operating system's lex is insufficient to compile&lt;BR /&gt; libpcap.  flex is a lex replacement that has many advantages, including&lt;BR /&gt; being able to compile libpcap.  For more information, see&lt;BR /&gt; &lt;A href="http://www.gnu.org/software/flex/flex.html" target="_blank"&gt;http://www.gnu.org/software/flex/flex.html&lt;/A&gt; .</description>
      <pubDate>Mon, 28 Aug 2006 14:09:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999712#M542097</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2006-08-28T14:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999713#M542098</link>
      <description>Just from a quick google search it looks like you need GNU m4 instead of the ccs m4.&lt;BR /&gt;&lt;BR /&gt;If you have the GNU m4 installed, try playing with your PATH or maybe set an M4 environment variable and re-running configure.</description>
      <pubDate>Mon, 28 Aug 2006 14:24:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999713#M542098</guid>
      <dc:creator>Jonathan Fife</dc:creator>
      <dc:date>2006-08-28T14:24:09Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999714#M542099</link>
      <description>Go into the configure script and look for "insufficient" and you should see something like:&lt;BR /&gt;&lt;BR /&gt;echo $ECHO_N "checking for capable lex... $ECHO_C" &amp;gt;&amp;amp;6&lt;BR /&gt;if test "${tcpdump_cv_capable_lex+set}" = set; then&lt;BR /&gt;  echo $ECHO_N "(cached) $ECHO_C" &amp;gt;&amp;amp;6&lt;BR /&gt;else&lt;BR /&gt;  if lex -t scanner.l &amp;gt; /dev/null 2&amp;gt;&amp;amp;1; then&lt;BR /&gt;                        tcpdump_cv_capable_lex=yes&lt;BR /&gt;                else&lt;BR /&gt;                        tcpdump_cv_capable_lex=insufficient&lt;BR /&gt;                fi&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;run that lex command by hand.  You will probably see something like:&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;"scanner.l" line 349: error 4: Parse tree too big&lt;BR /&gt;6000/6000 nodes(%e), 0/25000 positions(%p), 1/2000 (%n), 0 transitions, 0/4000 packed char classes(%k), 0/16000 packed transitions(%a), 0/19000 output slots(%o)&lt;BR /&gt;&lt;BR /&gt;Notice the bit about "nodes(%e)" - go into scanner.l and change the %e to something larger.  You should see something akin to:&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;6056/9000 nodes(%e), 22089/25000 positions(%p), 1312/2000 (%n), 48325 transitions, 3621/4000 packed char classes(%k), 14716/16000 packed transitions(%a), 17206/19000 output slots(%o)&lt;BR /&gt;&lt;BR /&gt;and re-run configure and all should be well.  From time to time I've provided the tcpdump/libpcap folks with patches along those lines, but things can grow and get beyond the patches and so configure becomes unhappy again.</description>
      <pubDate>Mon, 28 Aug 2006 15:31:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999714#M542099</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-08-28T15:31:27Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999715#M542100</link>
      <description>That worked!  YIPPEE and thank you thank you!&lt;BR /&gt;&lt;BR /&gt;Now, went on to compile TCPDUMP (configure --without-gcc) and print-dccp.c bit failed.  Found this link, also from Rick, &lt;A href="http://www.tcpdump.org/lists/workers/2005/11/msg00013.html" target="_blank"&gt;http://www.tcpdump.org/lists/workers/2005/11/msg00013.html&lt;/A&gt;&lt;BR /&gt;did what it said and got past that.&lt;BR /&gt;&lt;BR /&gt;NOW, i'm hitting another compile error and NOT getting anything with Google (at least that i could understand):&lt;BR /&gt;&lt;BR /&gt;cc: "print-isoclns.c", line 1619: error 1594: The sizeof operator cannot be applied to types with unknown size.&lt;BR /&gt;cc: "print-isoclns.c", line 1649: error 1594: The sizeof operator cannot be applied to types with unknown size.&lt;BR /&gt;*** Error exit code 1&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Aug 2006 12:04:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999715#M542100</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2006-08-29T12:04:43Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999716#M542101</link>
      <description>Which revision of tcpdump are you trying to compile?  What does it look like the variables might be at those lines of code, and can you find where they are actually defined?  Perhaps there is a missing include file, or perhaps the configure script ass-u-me-d something about 11.0 that was not true.</description>
      <pubDate>Tue, 29 Aug 2006 12:25:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999716#M542101</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-08-29T12:25:13Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999717#M542102</link>
      <description>version, latest (i think) 3.9.4&lt;BR /&gt;&lt;BR /&gt;looked at code at those lines:&lt;BR /&gt;&lt;BR /&gt;1619      u_int8_t prefix[sizeof(struct in6_addr)]; /* shared copy buffer for IPv4 and IPv6 prefixes */&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;1649      memset(prefix, 0, sizeof(struct in6_addr));              /* clear the copy buffer */&lt;BR /&gt;&lt;BR /&gt;So it looks like "in6_addr" is the variable, and it seems to be talked about in ip6 areas of code.&lt;BR /&gt;&lt;BR /&gt;And thanks for all your help.  Thanks so much.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Aug 2006 12:40:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999717#M542102</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2006-08-29T12:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999718#M542103</link>
      <description>Right - and while 11.0 may have done some "pre-enablement" for IPv6 it doesn't really have support for IPv6.  So, if there is a configure option to disable using host IPv6 you should use it and see if that lets things go a bit better.&lt;BR /&gt;&lt;BR /&gt;And if that _does_ work, please forward all the details to the tcpdump-workers mailing list - including what you needed to change to make lex happy.</description>
      <pubDate>Tue, 29 Aug 2006 12:44:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999718#M542103</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-08-29T12:44:27Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999719#M542104</link>
      <description>Oh that makes such good sense, i must have done it wrong, though.  Here's the whole sad tale:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;r:/home/root/tcpdump/tcpdump-3.9.4&amp;gt; ./configure --disable-ipv6 --without-gcc&lt;BR /&gt;checking build system type... hppa2.0w-hp-hpux11.00&lt;BR /&gt;checking host system type... hppa2.0w-hp-hpux11.00&lt;BR /&gt;checking for gcc... cc&lt;BR /&gt;checking for C compiler default output... a.out&lt;BR /&gt;checking whether the C compiler works... yes&lt;BR /&gt;checking whether we are cross compiling... no&lt;BR /&gt;checking for suffix of executables... &lt;BR /&gt;checking for suffix of object files... o&lt;BR /&gt;checking whether we are using the GNU C compiler... no&lt;BR /&gt;checking whether cc accepts -g... yes&lt;BR /&gt;checking for cc option to accept ANSI C... none needed&lt;BR /&gt;checking that cc handles ansi prototypes... yes&lt;BR /&gt;checking for inline... __inline&lt;BR /&gt;checking for __attribute__... no&lt;BR /&gt;checking how to run the C preprocessor... cc -E&lt;BR /&gt;checking for egrep... grep -E&lt;BR /&gt;checking for ANSI C header files... yes&lt;BR /&gt;checking for sys/types.h... yes&lt;BR /&gt;checking for sys/stat.h... yes&lt;BR /&gt;checking for stdlib.h... yes&lt;BR /&gt;checking for string.h... yes&lt;BR /&gt;checking for memory.h... yes&lt;BR /&gt;checking for strings.h... yes&lt;BR /&gt;checking for inttypes.h... yes&lt;BR /&gt;checking for stdint.h... no&lt;BR /&gt;checking for unistd.h... yes&lt;BR /&gt;checking fcntl.h usability... yes&lt;BR /&gt;checking fcntl.h presence... yes&lt;BR /&gt;checking for fcntl.h... yes&lt;BR /&gt;checking rpc/rpcent.h usability... no&lt;BR /&gt;checking rpc/rpcent.h presence... no&lt;BR /&gt;checking for rpc/rpcent.h... no&lt;BR /&gt;checking netdnet/dnetdb.h usability... no&lt;BR /&gt;checking netdnet/dnetdb.h presence... no&lt;BR /&gt;checking for netdnet/dnetdb.h... no&lt;BR /&gt;checking for netinet/if_ether.h... no&lt;BR /&gt;configure: Rechecking with some additional includes&lt;BR /&gt;checking for netinet/if_ether.h... yes&lt;BR /&gt;checking whether time.h and sys/time.h may both be included... yes&lt;BR /&gt;checking smi.h usability... no&lt;BR /&gt;checking smi.h presence... no&lt;BR /&gt;checking for smi.h... no&lt;BR /&gt;checking for smiInit in -lsmi... no&lt;BR /&gt;checking whether to enable the possibly-buggy SMB printer... yes&lt;BR /&gt;configure: WARNING: The SMB printer may have exploitable buffer overflows!!!&lt;BR /&gt;checking whether to drop root privileges by default... no&lt;BR /&gt;checking whether to chroot... no&lt;BR /&gt;checking whether to enable ipv6... no&lt;BR /&gt;checking for dnet_htoa declaration in netdnet/dnetdb.h... no&lt;BR /&gt;checking for char... yes&lt;BR /&gt;checking size of char... 1&lt;BR /&gt;checking for short... yes&lt;BR /&gt;checking size of short... 2&lt;BR /&gt;checking for int... yes&lt;BR /&gt;checking size of int... 4&lt;BR /&gt;checking for long... yes&lt;BR /&gt;checking size of long... 4&lt;BR /&gt;checking for long long... yes&lt;BR /&gt;checking size of long long... 8&lt;BR /&gt;checking for addrinfo... no&lt;BR /&gt;checking for NI_MAXSERV... no&lt;BR /&gt;checking for NI_NAMEREQD... no&lt;BR /&gt;checking for sockaddr_storage... no&lt;BR /&gt;checking for INADDRSZ... yes&lt;BR /&gt;checking for IN6ADDRSZ... no&lt;BR /&gt;checking for RES_USE_INET6... no&lt;BR /&gt;checking for res_state_ext... no&lt;BR /&gt;checking for nsort in res_state... no&lt;BR /&gt;checking for vfprintf... yes&lt;BR /&gt;checking for strcasecmp... yes&lt;BR /&gt;checking for strlcat... no&lt;BR /&gt;checking for strlcpy... no&lt;BR /&gt;checking for strdup... yes&lt;BR /&gt;checking for strsep... no&lt;BR /&gt;checking for strftime... no&lt;BR /&gt;checking for setlinebuf... no&lt;BR /&gt;checking for alarm... yes&lt;BR /&gt;checking for vsnprintf... yes&lt;BR /&gt;checking for snprintf... yes&lt;BR /&gt;checking return type of signal handlers... void&lt;BR /&gt;checking for sigaction... yes&lt;BR /&gt;checking for library containing dnet_htoa... no&lt;BR /&gt;checking for main in -lrpc... no&lt;BR /&gt;checking for library containing getrpcbynumber... -lnsl&lt;BR /&gt;checking for library containing gethostbyname... none required&lt;BR /&gt;checking for library containing socket... none required&lt;BR /&gt;checking for library containing putmsg... none required&lt;BR /&gt;checking for local pcap library... not found&lt;BR /&gt;checking for main in -lpcap... yes&lt;BR /&gt;checking for extraneous pcap header directories... not found&lt;BR /&gt;checking for pcap_list_datalinks... yes&lt;BR /&gt;checking for pcap_set_datalink... yes&lt;BR /&gt;checking for pcap_datalink_name_to_val... yes&lt;BR /&gt;checking for pcap_datalink_val_to_description... yes&lt;BR /&gt;checking for pcap_breakloop... yes&lt;BR /&gt;checking for pcap_dump_ftell... yes&lt;BR /&gt;checking for inet_ntop... no&lt;BR /&gt;checking for inet_pton... no&lt;BR /&gt;checking for inet_aton... yes&lt;BR /&gt;checking for ether_ntohost... no&lt;BR /&gt;checking if sockaddr struct has sa_len member... no&lt;BR /&gt;checking for pcap_findalldevs... yes&lt;BR /&gt;checking for pcap_dump_flush... yes&lt;BR /&gt;checking for pcap_lib_version... yes&lt;BR /&gt;checking for pcap_if_t... yes&lt;BR /&gt;checking whether pcap_debug is defined by libpcap... no&lt;BR /&gt;checking whether yydebug is defined by libpcap... yes&lt;BR /&gt;checking for bpf_dump... yes&lt;BR /&gt;checking sys/bitypes.h usability... no&lt;BR /&gt;checking sys/bitypes.h presence... no&lt;BR /&gt;checking for sys/bitypes.h... no&lt;BR /&gt;checking for int8_t... yes&lt;BR /&gt;checking for u_int8_t... no&lt;BR /&gt;checking for int16_t... yes&lt;BR /&gt;checking for u_int16_t... no&lt;BR /&gt;checking for int32_t... yes&lt;BR /&gt;checking for u_int32_t... no&lt;BR /&gt;checking for int64_t... yes&lt;BR /&gt;checking for u_int64_t... no&lt;BR /&gt;checking for inttypes.h... (cached) yes&lt;BR /&gt;checking whether inttypes.h defines the PRI[doxu]64 macros... yes&lt;BR /&gt;checking if sockaddr struct has sa_len member... no&lt;BR /&gt;checking if unaligned accesses fail... yes&lt;BR /&gt;checking for h_errno... yes&lt;BR /&gt;checking for SSLeay... no&lt;BR /&gt;checking for a BSD-compatible install... /opt/imake/bin/install -c&lt;BR /&gt;configure: creating ./config.status&lt;BR /&gt;config.status: creating Makefile&lt;BR /&gt;config.status: creating config.h&lt;BR /&gt;config.status: executing default-1 commands&lt;BR /&gt;r:/home/root/tcpdump/tcpdump-3.9.4&amp;gt; make&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./addrtoname.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./cpack.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./gmpls.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./oui.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./gmt2local.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./ipproto.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./nlpid.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./l2vpn.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./machdep.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./parsenfsfh.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-802_11.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-ap1394.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-ah.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-arcnet.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-aodv.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-arp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-ascii.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-atalk.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-atm.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-beep.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-bfd.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-bgp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-bootp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-cdp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-chdlc.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-cip.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-cnfp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-dccp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-decnet.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-domain.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-dvmrp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-enc.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-egp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-eap.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-eigrp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-esp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-ether.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-fddi.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-fr.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-gre.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-hsrp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-icmp.c&lt;BR /&gt;cc: "print-icmp.c", line 406: warning 611: Type conversion loses "const" qualifier.&lt;BR /&gt;cc: "print-icmp.c", line 406: warning 563: Argument #3 is not the correct type.&lt;BR /&gt;cc: "print-icmp.c", line 416: warning 611: Type conversion loses "const" qualifier.&lt;BR /&gt;cc: "print-icmp.c", line 416: warning 563: Argument #3 is not the correct type.&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-igmp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-igrp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-ip.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-ipcomp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-ipfc.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-ipx.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-isakmp.c&lt;BR /&gt;        cc -O -DHAVE_CONFIG_H  -I./missing  -D_U_="" -I.  -I/usr/local/include -I./missing -c ./print-isoclns.c&lt;BR /&gt;cc: "print-isoclns.c", line 1619: error 1594: The sizeof operator cannot be applied to types with unknown size.&lt;BR /&gt;cc: "print-isoclns.c", line 1649: error 1594: The sizeof operator cannot be applied to types with unknown size.&lt;BR /&gt;*** Error exit code 1&lt;BR /&gt;&lt;BR /&gt;Stop.</description>
      <pubDate>Tue, 29 Aug 2006 13:03:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999719#M542104</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2006-08-29T13:03:02Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999720#M542105</link>
      <description>While it would be a blunt instrument, given the liklihood of seeing any ISO CLNS traffic, you could probably  see about making that an empty file, or perhaps editing the Makefile.in to remove it from the build.&lt;BR /&gt;&lt;BR /&gt;And backing-up a bit, given the status of 11.0, it might be a _very_ good idea to get those application restrictions addressed and get onto an OS from this century :)  11iv2 (aka 11.23) would be a good place to be.  Heck, it would probably still run your existing application binaries just fine.  Depending on how much "stuff" has to come along for the ride with those binaries, you might be able to try it out using one of the "testdrive" systems first:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.testdrive.hp.com/" target="_blank"&gt;http://www.testdrive.hp.com/&lt;/A&gt;</description>
      <pubDate>Tue, 29 Aug 2006 13:20:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999720#M542105</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-08-29T13:20:31Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999721#M542106</link>
      <description>Yeah, i know, i had looked into upgrading earlier this year...  didn't get a lot of buy in from the DBA's though.  Believe it or not, COBOL in the application is the issue.</description>
      <pubDate>Tue, 29 Aug 2006 13:22:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999721#M542106</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2006-08-29T13:22:55Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999722#M542107</link>
      <description>Wow, I have a usable "tcpdump"! &lt;BR /&gt;&lt;BR /&gt;"gutted" print-isoclns.c, and then got some errors at the end:&lt;BR /&gt;usr/ccs/bin/ld: Unsatisfied symbols:&lt;BR /&gt;   isoclns_print (first referenced in print-chdlc.o) (code)&lt;BR /&gt;&lt;BR /&gt;BUT it still made the executable, which does what i need it to do.&lt;BR /&gt;&lt;BR /&gt;So, Rick, i will GLADY write this up, but it seems not really "correct" enough.  Whatever you think, and i can't thank you enough for all your assistance.&lt;BR /&gt;&lt;BR /&gt;(i'm nagging about 11.0 -&amp;gt; 11.23 upgrades too)</description>
      <pubDate>Wed, 30 Aug 2006 11:48:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999722#M542107</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2006-08-30T11:48:52Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999723#M542108</link>
      <description>While the gutting isn't really the "right" fix, letting the tcpdump-workers mailing list know about the issue would be the first step towards fixing it.  &lt;BR /&gt;&lt;BR /&gt;As for the unresolved symbols bit, you could tweak the gutting by either removing calls to the routine from elsewhere, or making the routine a noop (ie just return) rather than not being there at all.&lt;BR /&gt;&lt;BR /&gt;Upgrading to newer OS and hardware will be thanks enough :)</description>
      <pubDate>Wed, 30 Aug 2006 12:17:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999723#M542108</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-08-30T12:17:16Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999724#M542109</link>
      <description>I know that you've got tcpdump working, but I hope you are aware of the fact that, "nettl" is a very powerful tool on hp-ux. You can grab all the network traffic (and do filtering on it). The dump file created, can be read &amp;amp; effortlessly decoded by Ethereal. So if you have the luxery of running Ethereal on a different host, and willing to FTP the capture-dump file around (just once actully), you have a very powerful combo.&lt;BR /&gt;&lt;BR /&gt;AFIAK, tcpdump cannot capture packets sent thru the localhost &amp;amp; also between applications sitting on same host (though using the non-localhost IP's for comm.). They simply don't reach deep enough in the network stack, for libpcap to be able to read them. This used to the fact until 2 yrs back, not sure if this has changed now.&lt;BR /&gt;&lt;BR /&gt;-bd</description>
      <pubDate>Fri, 01 Sep 2006 01:34:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999724#M542109</guid>
      <dc:creator>Banibrata Dutta</dc:creator>
      <dc:date>2006-09-01T01:34:58Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999725#M542110</link>
      <description>Indeed, one cannot use tcdpump to trace loopback traffic under HP-UX.  That is a limitation of promiscuous mode in HP-UX used by libpcap.  'Tcpdump' in and of itself doesn't care.&lt;BR /&gt;&lt;BR /&gt;WRT "local" traffic to the other assigned IPs, there is a bit of a kludge one could use if necessary.  You can used ndd to set "ip_loopback_bypass" to force traffic to local IPs to go to the driver(s).  This then sends them past the promiscuous taps and so the traffic should become visible to libpcap.  IIRC "ip_loopback_bypass" is in the "unsupported" category (eg be careful kids)</description>
      <pubDate>Fri, 01 Sep 2006 11:35:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999725#M542110</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-09-01T11:35:20Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999726#M542111</link>
      <description>Thanks, Barbara, and yes, i was aware of nettl, and have even tried to use it, but i just wasn't smart enough, i guess, to understand what i needed to do.&lt;BR /&gt;&lt;BR /&gt;Maybe the idea that i could dump and ftp to a machine with ethereal might change my mind, but nettl made me feel dumb.</description>
      <pubDate>Fri, 01 Sep 2006 12:24:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999726#M542111</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2006-09-01T12:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999727#M542112</link>
      <description>&lt;P&gt;It is true to using "nettl" to capture IP traffic might seem a little daunting at first, but once you get hang of it, it's a easy. &lt;BR /&gt;&lt;BR /&gt;Here's a little how-to:&lt;BR /&gt;&lt;BR /&gt;1) Stop all tracing&lt;BR /&gt;nettl -tf -e all &lt;BR /&gt;&lt;BR /&gt;2) Start IP traffic capture, and then Start the TCP/IP test case nettl -tn all -e ns_ls_ip -usize 1024 -tracemax 99999 -f /tmp/tf&lt;BR /&gt;&lt;BR /&gt;3) Stop all tracing&lt;BR /&gt;nettl -tf -e all &lt;BR /&gt;&lt;BR /&gt;After tracing is stopped, you'd fine one or two files in /tmp/tf000 &amp;amp; maybe /tmp/tf001.&lt;BR /&gt;&lt;BR /&gt;These files are directly readable by Ethereal/Wireshark, with all it's glorious decoding.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2021 07:05:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999727#M542112</guid>
      <dc:creator>Banibrata Dutta</dc:creator>
      <dc:date>2021-09-08T07:05:54Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999728#M542113</link>
      <description>fyi, i sent the saga off to tcpdump-workers.&lt;BR /&gt;&lt;BR /&gt;also, i do appreciate the hint on using nettl, i'm going to give it a try!</description>
      <pubDate>Tue, 05 Sep 2006 11:34:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999728#M542113</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2006-09-05T11:34:36Z</dc:date>
    </item>
    <item>
      <title>Re: libpcap (for tcpdump) compile</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999729#M542114</link>
      <description>problem solved and documented</description>
      <pubDate>Tue, 21 Aug 2007 09:48:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/libpcap-for-tcpdump-compile/m-p/4999729#M542114</guid>
      <dc:creator>Lynne Seamans</dc:creator>
      <dc:date>2007-08-21T09:48:20Z</dc:date>
    </item>
  </channel>
</rss>

