Re: IPv4 NAT doesn't compile in 2.4.4

2001-05-01 Thread Rusty Russell
In message <[EMAIL PROTECTED]> you write: > net/network.o: In function `init_or_cleanup': > net/network.o(.text+0x4a530): relocation truncated to fit: R_ARM_PC24 ip_nat_ cleanup My bad: Russell, you're absolutely right. Obvious fix below. Thanks! Rusty. diff -urN -I \$.*\$ -X /tmp/kerndiff.guo

Re: IPv4 NAT doesn't compile in 2.4.4

2001-04-28 Thread David S. Miller
Russell King writes: > >From x86 vmlinux.lds: > > /* Sections to be discarded */ > /DISCARD/ : { > *(.text.exit) > *(.data.exit) > *(.exitcall.exit) > } Thanks, this is the part I didn't catch. If you had said this in the first email, I would have un

Re: IPv4 NAT doesn't compile in 2.4.4

2001-04-28 Thread Russell King
On Sat, Apr 28, 2001 at 02:07:53PM -0700, David S. Miller wrote: > Why would ip_nat_cleanup() be removed by the linker? Because we explicitly tell the linker to drop all code marked as __exit: #define __exit __attribute__ ((unused, __section__(".text.exit"))) >From x86 vmlinux.lds:

Re: IPv4 NAT doesn't compile in 2.4.4

2001-04-28 Thread David S. Miller
Russell King writes: > ip_nat_standalone.c: > > static int init_or_cleanup(int init) > { > ... > cleanup_nat: > ip_nat_cleanup(); > ... > } Call ip_nat_cleanup(); > ip_nat_core: > > void __exit ip_nat_cleanup(void) > { > ip_ct_selective_cleanup(&clean_nat, NULL)

IPv4 NAT doesn't compile in 2.4.4

2001-04-28 Thread Russell King
net/network.o: In function `init_or_cleanup': net/network.o(.text+0x4a530): relocation truncated to fit: R_ARM_PC24 ip_nat_cleanup says it all. ip_nat_standalone.c: static int init_or_cleanup(int init) { ... cleanup_nat: ip_nat_cleanup(); ... } ip_nat_core: void __exit ip_nat_cleanup