FW: Problems building argus on non-i386 systems.

[Carter Bullard]

Hey Yotam,
   I believe the problem is in the defintion of __BYTE_ORDER. If
__BYTE_ORDER is not defined, then these fields will not exist in "struct
ip".  Argus must not be doing the right thing in determining
endian'ness.

   I assume that Debian does the standard linux include file
/usr/include/endian.h?  Lets try this patch for the file
./include/compat.h, to see if it isn't the simplest way to fix the
problem.

Carter

Carter Bullard
QoSient, LLC
300 E. 56th Street, Suite 18K
New York, New York  10022

carter at qosient.com
Phone +1 212 588-9133
Fax   +1 212 588-9134
http://qosient.com 



Index: compat.h
===================================================================
RCS file: /usr/local/cvsroot/argus/include/compat.h,v
retrieving revision 1.7.4.3
diff -r1.7.4.3 compat.h
52a53,60
> #if defined(HAVE_SOLARIS)
> #include <sys/byteorder.h>
> #endif
> 
> if defined(linux)
> #include <endian.h>
> #endif
> 

-----Original Message-----
From: owner-argus-info at lists.andrew.cmu.edu
[mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of Yotam Rubin
Sent: Sunday, June 03, 2001 2:14 PM
To: argus-info at lists.andrew.cmu.edu
Subject: Re: Problems building argus on non-i386 systems.


On Sun, Jun 03, 2001 at 09:53:14AM -0400, Carter Bullard wrote:
> Hey Yotam,
>    Yes argus compiles fine on Solaris.  Somehow its finding
> a <netinet/ip.h> that has a non-BSD type of "struct ip" defined. These
> are Debian machines?  What does the standard Debian 
> /usr/include/netinet/ip.h look like?

I've attached ip.h to this letter, but I suspect the culprit is not
netinet/ip.h, as there are no differences between the i386 and the
sparc/arm version of the discussed file.

    The difference between architectures is manifested in the contents
of 
/usr/include/bits and /usr/include/asm, so we might want to look there.
I cannot be more specific since I do not have access to non-i386 Debian
systems.

	Regards, Yotam Rubin

> 
> Carter
> 
> Carter Bullard
> QoSient, LLC
> 300 E. 56th Street, Suite 18K
> New York, New York  10022
> 
> carter at qosient.com
> Phone +1 212 588-9133
> Fax   +1 212 588-9134
> http://qosient.com
> 
> 
> -----Original Message-----
> From: owner-argus-info at lists.andrew.cmu.edu
> [mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of Yotam
> Rubin
> Sent: Sunday, June 03, 2001 8:12 AM
> To: argus-info at lists.andrew.cmu.edu
> Subject: Problems building argus on non-i386 systems.
> 
> 
> Greetings,
> 
>         Has anyone successfully compiled argus on a non-i386 system?
> The following problem is manifested on many architectures such as 
> sparc and arm I don't have access to a non-i386 system so I cannot 
> reliably debug the problem.
> 
> 	Relevant error messages follow:
> "gcc -O -I . -I../include  -I../include/linux-include
> -DHAVE_MALLOC_H=1
> +-DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DHAVE_NET_IF_ARP_H=1  -c 
> +./ArgusModeler.c
> ./ArgusModeler.c: In function `ArgusDiscoverNetworkProtocol':
> ./ArgusModeler.c:218: structure has no member named `ip_v'
> ./ArgusModeler.c:218: structure has no member named `ip_hl'
> ./ArgusModeler.c: In function `ArgusCreateIPFlow':
> ./ArgusModeler.c:1504: structure has no member named `ip_hl'
> ./ArgusModeler.c:1532: structure has no member named `ip_hl'
> make[2]: *** [ArgusModeler.o] Error 1"
> 
> 
>         -- Yotam Rubin
> 
>