> We have found the CVS version of tcpdump to be indispensable in 
> helping us debug L2TP problems. I have been tracking your work for 
> the past year.
> 
> Since January 7, i've not been able to compile tcpdump. It is failing 
> with
> 
> gcc -I/usr/local/include -L/usr/local/lib -O2 -DHAVE_CONFIG_H -I. -I../libpcap  
>-I./missing -I/usr/include -c ./print-dhcp6.c
> ./print-dhcp6.c: In function `dhcp6_print':
> ./print-dhcp6.c:200: `dhcp6' defined as wrong kind of tag
> *** Error code 1
> 
> This is on FreeBSD 4.5-RC. Is this a FreeBSD only problem?

Unlikely, given that

        1) I've compiled it successfully on FreeBSD 3.4

and

        2) the error is that the word "union" in that line should be
           "struct", because "print-dhcp6" doesn't define "union dhcp6"
           but does define "struct dhcp6".

It's an IPv6-enabled-only problem - my 3.4 machine doesn't have any IPv6
support, which is why it compiles.  (Currently, the IPv6 support in
tcpdump isn't enabled at all unless you have sufficient IPv6 support on
the machine on which you're compiling it; I think that we can fix that
so that you get at least some V6 support without it, even if you don't
get address-to-name resolution, but that involves defining our own data
type for IPv6 addresses rather than using one defined by the platform.)

Try changing "union" to "struct" in that line, and let us know if that
fixes the problem; if so, I'll check in a fix.  (If you interpret "let
us know" as "let me know", then let me know by sending mail to
"[EMAIL PROTECTED]", or "[EMAIL PROTECTED]", not by sending mail to
"[EMAIL PROTECTED]" - I can check stuff in from home, but not from work, so
if you reply to "[EMAIL PROTECTED]" and the mail arrives when I'm at work,
the checkin will be delayed....)

I've no idea why things changed on January 7, given that the change that
probably broke things was checked in on January 10....
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe

Reply via email to