Czy iptables buduje się na 2.4.22 ?

Jacek Sobczak jsobczak w op.pl
Sob, 4 Paź 2003, 13:58:49 CEST


Bo u mnie się nie buduje:
sopel w speedy SPECS$ ./builder -v -bb --without patchedkernel --without  
howto iptables.spec

[...]

i686-pld-linux-gcc -O2 -march=i686 -DNDEBUG -Wall -Wunused -I/usr/src/ 
linux/include -Iinclude/ -DIPTABLES_VERSION=\"1.2.8\"  -fPIC -o  
extensions/libipt_physdev_sh.o -c extensions/libipt_physdev.c
extensions/libipt_physdev.c: In function `parse':
extensions/libipt_physdev.c:86: error: `IPT_PHYSDEV_OP_MATCH_IN'  
undeclared (first use in this function)
extensions/libipt_physdev.c:86: error: (Each undeclared identifier is  
reported only once
extensions/libipt_physdev.c:86: error: for each function it appears  
in.)
extensions/libipt_physdev.c:97: error: `IPT_PHYSDEV_OP_MATCH_OUT'  
undeclared (first use in this function)
extensions/libipt_physdev.c: In function `print':
extensions/libipt_physdev.c:144: error: `IPT_PHYSDEV_OP_MATCH_IN'  
undeclared (first use in this function)
extensions/libipt_physdev.c:146: error: `IPT_PHYSDEV_OP_MATCH_OUT'  
undeclared (first use in this function)
extensions/libipt_physdev.c: In function `save':
extensions/libipt_physdev.c:156: error: `IPT_PHYSDEV_OP_MATCH_IN'  
undeclared (first use in this function)
extensions/libipt_physdev.c:158: error: `IPT_PHYSDEV_OP_MATCH_OUT'  
undeclared (first use in this function)
make: *** [extensions/libipt_physdev_sh.o] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.73188 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.73188 (%build)
Error: package build failed. (no more info)

Co można z tym zrobić ?
Jacek



Więcej informacji o liście dyskusyjnej pld-users-pl