Thanks, Matthew, that is exactly what I ended up doing. I sent Don my
recommendations for doing the same. I hope that it was somewhat helpful.
Don (the first one)
On 4/7/2011 6:22 AM, Matthew Smith wrote:
Hi - while it's possible to run some OABI user space programs on an
EABI kernel compiled with OABI_COMPAT there are a number of caveats -
the biggest one that affects iptables is the way data structures are
passed from user space to the kernel using ioctl calls - compiling
iptables statically doesn't help as iptables is a user space interface
to kernel mode packet filter features. Only solution here is to run an
EABI userland - any reason why you couldn't do that?
See links below for more info:
http://wiki.debian.org/ArmEabiPort
http://permalink.gmane.org/gmane.linux.ports.arm.kernel/58165
http://forum.soft32.com/linux/EABI-OABI-incompatibility-ftopict312450.html
--- In <ts-7000%40yahoogroups.com>,
"Donb" <> wrote:
>
> Hi Don,
>
> Did you ever get IPtables working? I danced this around with
Technologic but didn't find the right combination.
>
> Thanks,
> Don
>
>
> --- In <ts-7000%40yahoogroups.com>,
"Rekcut_Nod" <dtucker@> wrote:
> >
> > As an update, someone suggested that there might be an issue with
EABI vs. OABI on the ARM platform, so I reconfigured iptables with
--enable-static and --disable-dynamic, since I think that there is not
an issue as long as iptables doesn't try to build linking to the
EABI-built kernel libraries. After rebuilding, I tried to run
"iptables -L" again and this time received a different error:
> >
> > "getsockopt failed strangely: invalid argument"
> >
> > As before, if anyone has any suggestions on how I might resolve
this error to get iptables working, I'd be very appreciative.
> >
> > Thanks,
> > Don
> >
>
smime.p7s
Description: S/MIME Cryptographic Signature
|