 | | | Nistnet building failure | Nistnet building failure 2003-11-17 - By Eric-Olivier Lamey
Back
Hi everyone,
I am trying to build nisnet on a RHEL 3 AS, and it fails apparently
because of some kernel headers. It builds fine on RH 9 however.
Here is the error:
make[1]: Entering directory `/home/package/packages/nistnet/nistnet/lib '
gcc -I. -I../include -Wall -Wstrict-prototypes -fno-strength-reduce -pipe
-m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2
-DDEVHITBOX=\ "/dev/hitbox\ " -DHITMAJOR=62 -DHITMINOR=0
-DDEVNISTNET=\ "/dev/nistnet\ " -DNISTNETMAJOR=62 -DNISTNETMINOR=1
-DDEVMUNGEBOX=\ "/dev/mungebox\ " -DMUNGEMAJOR=63 -DDEVSPYBOX=\ "/dev/spybox\ "
-DSPYMAJOR=64 -DCONFIG_ECN -DCONFIG_DELAYSTART -DCONFIG_RTC_AGGRESSIVE -O
-I.. -I../include -c -o nistnetlib.o nistnetlib.c
`-m486 ' is deprecated. Use `-march=i486 ' or `-mcpu=i486 ' instead.
cc1: warning: -malign-loops is obsolete, use -falign-loops
cc1: warning: -malign-jumps is obsolete, use -falign-jumps
cc1: warning: -malign-functions is obsolete, use -falign-functions
In file included from ../include/uincludes.h:34,
from nistnetlib.c:12:
../include/nistnet.h:170: field `igmp ' has incomplete type
make[1]: *** [nistnetlib.o] Error 1
make[1]: Leaving directory `/home/package/packages/nistnet/nistnet/lib '
make: *** [sub_dirs] Error 2
The offending lines in nistnet.h are:
#if defined(__GLIBC__) && !defined(__KERNEL__)
/*#include <net/protocol.h >*/
#include <netinet/ip.h >
#include <netinet/tcp.h >
#include <netinet/udp.h >
#include <netinet/ip_icmp.h >
#include <netinet/igmp.h >
#else
#include <linux/netdevice.h >
#include <linux/ip.h >
#include <linux/tcp.h >
#include <linux/udp.h >
#include <linux/icmp.h >
#ifdef __KERNEL__
#include <net/protocol.h >
#endif
#include <linux/igmp.h >
#endif
struct lin_mungestats {
struct iphdr ip;
union {
struct tcphdr tcp;
struct udphdr udp;
struct icmphdr icmp;
struct igmphdr igmp;
} h;
};
The versions of the relevant packages are:
nistnet 2.0.12
kernel-2.4.21-4.0.1.EL
kernel-source-2.4.21-4.0.1.EL
gcc-3.2.3-20
glibc-2.3.2-95.3
glibc-kernheaders-2.4-8.34
Does anyone have an idea of what the problem might be ?
P.S: sorry for the long lines...
--
Eric-Olivier Lamey
System administrator
UbiSoft Montr�al
|
|
|