From: Denys Vlasenko <vda.linux@googlemail.com>
To: busybox@busybox.net
Cc: Saravanan Chanemouganandam <schane@osmozis.com>,
netfilter@vger.kernel.org, linux-arm@lists.arm.linux.org.uk
Subject: Re: iptables - Couldn't load target error
Date: Thu, 20 Dec 2007 10:03:26 +0000 [thread overview]
Message-ID: <200712201003.26454.vda.linux@googlemail.com> (raw)
In-Reply-To: <200712191221.58597.schane@osmozis.com>
On Wednesday 19 December 2007 11:21, Saravanan Chanemouganandam wrote:
> Hi all,
>
> I have some problem with iptables (v1.3.8) and extension supports libraries
> installed to the buildroot's root filesystem (/lib/iptables) running on
> Xscale pxa270.
>
> iptables with MASQUERADE support throws Couldn't load target error. The
> following strace shows that it tries to open libraries in the /lib and in
> the /usr/lib instead of /lib/iptables.
Last time I built iptables from source it was iptables-1.3.5.
iptables are not using de-facto standard "configure+make"
install process, they take make variables instead.
Mine was built with:
# Do NOT point it to non-pristine kernel tree!
# (seen horrible miscompilation on 32:64 user:kernel x86_64)
KERNEL_DIR=/usr/src/kernel/delay/linux-2.6.17.11.src
make KERNEL_DIR="$KERNEL_DIR" BINDIR=... LIBDIR=... MANDIR=...
I guess you built your iptables with wrong/unset LIBDIR.
People were right pointing out that this is not busybox related question.
--
vda
next prev parent reply other threads:[~2007-12-20 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 11:21 iptables - Couldn't load target error Saravanan Chanemouganandam
2007-12-19 11:56 ` Alexander Griesser
2007-12-19 12:48 ` Mike Frysinger
2007-12-20 10:03 ` Denys Vlasenko [this message]
2007-12-20 13:49 ` Saravanan Chanemouganandam
2007-12-20 17:26 ` Denys Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200712201003.26454.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=busybox@busybox.net \
--cc=linux-arm@lists.arm.linux.org.uk \
--cc=netfilter@vger.kernel.org \
--cc=schane@osmozis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.