gned to: Nobody (None)
Summary: FTBFS tcpdump-3.8.3
Category: posix
Group: unsubmitted
>Resolution: Fixed
Initial Comment:
Author: Barry deFreese
Source: tcpdump
Status: ugly but builds
Categories: posix
Strip-Level: -p1
--- tcpdump-stdinc.horg 2005-02-10 18:33:19.0 -0500
+++ tcpdum
Barry deFreese <[EMAIL PROTECTED]> writes:
Hi Barry,
> If built tcpdump-3.8.3 tonight with the following lame patch:
Did you get tcpdump to work on GNU/Hurd?
I seriously doubt that it would work, because I expect that there is
no way to access the NIC directly.
--
Marco
--
To UN
At Thu, 10 Feb 2005 20:57:06 -0800,
Barry deFreese wrote:
> +#if defined(__GNU__)
> +# define MAXHOSTNAMELEN 64
> +#endif
tcpdump.
print-atalk.c uses MAXHOSTNAMELEN this way:
char nambuf[MAXHOSTNAMELEN + 20];
... getting lines from "/etc/atalk.names" into ...
char line[
debian-guest)
Assigned to: Nobody (None)
Summary: FTBFS tcpdump-3.8.3
Initial Comment:
Author: Barry deFreese <[EMAIL PROTECTED]>
Source: tcpdump
Status: ugly but builds
Categories: posix
Strip-Level: -p1
--- tcpdump-stdinc.horg 2005-02-10 18:33:19.0 -0500
+++ tcpdump-stdinc.h
On Fri, Feb 11, 2005 at 04:30:08PM +0100, Alfred M. Szmidt wrote:
> What do they use it for?
Look at the source, I think its a bit hard to describe.
Michael
--
Michael Banck
Debian Developer
[EMAIL PROTECTED]
http://www.advogato.org/person/mbanck/diary.html
--
To UNSUBSCRIBE, email to [EMAI
I agree. However, what is funny is that they aren't even using
MAXHOSTNAMELEN for the buffer for gethostname() as usual so it's a weird
situation anyway.
Lets fix the program the correct way instead of making hacks like
this. What do they use it for?
--
To UNSUBSCRIBE, email to [EMAI
- Original Message -
From: "Alfred M. Szmidt" <[EMAIL PROTECTED]>
To: "Barry Comcast" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>;
Sent: Friday, February 11, 2005 9:52 AM
Subject: Re: tcpdump-3.8.3
>Why? Their code uses 64 and my Deb
On Fri, Feb 11, 2005 at 09:43:30AM -0500, Barry Comcast wrote:
> > #define MAXHOSTNAMELEN 4096
>
> Why? Their code uses 64 and my Debian GNU/Linux box has MAXHOSTNAMELEN
> defined as 64??
OK then, I thought it was the other value. my bad.
Michael
--
Michael Banck
Debian Developer
[EMAIL PROT
Why? Their code uses 64 and my Debian GNU/Linux box has
MAXHOSTNAMELEN defined as 64??
Because we don't have a limit to begin with, this is just a ugly way
of saying that we don't have one. But this is really not important,
what is the problem with just fixing it the proper way and use
xge
- Original Message -
From: "Michael Banck" <[EMAIL PROTECTED]>
To:
Sent: Friday, February 11, 2005 4:58 AM
Subject: Re: tcpdump-3.8.3
> On Thu, Feb 10, 2005 at 08:57:06PM -0800, Barry deFreese wrote:
> > --- tcpdump-stdinc.horg 2005-02-10 18:33:19.00
On Thu, Feb 10, 2005 at 08:57:06PM -0800, Barry deFreese wrote:
> --- tcpdump-stdinc.horg 2005-02-10 18:33:19.0 -0500
> +++ tcpdump-stdinc.h2005-02-10 18:32:40.0 -0500
> @@ -42,6 +42,10 @@
> #ifndef tcpdump_stdinc_h
> #define tcpdump_stdinc_h
>
> +#if defined(__GNU__)
> +# defi
If built tcpdump-3.8.3 tonight with the following lame patch:
--- tcpdump-stdinc.horg 2005-02-10 18:33:19.0 -0500
+++ tcpdump-stdinc.h2005-02-10 18:32:40.0 -0500
@@ -42,6 +42,10 @@
#ifndef tcpdump_stdinc_h
#define tcpdump_stdinc_h
+#if defined(__GNU__)
+# define MAXHOSTNAMELEN
12 matches
Mail list logo
