Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Kevin Wilson <wkevils@gmail.com>
To: netfilter@vger.kernel.org
Subject: How to install xtables extension to arbitrary path when cross compiling iptables?
Date: Mon, 16 Apr 2012 15:19:00 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120416T170250-226@post.gmane.org> (raw)

how to install xtables extension to arbitrary path when cross compiling?


I have this issue, which I cannot resolve, 
when cross compiling iptables 1.4.8 
with 
./configure --prefix=/home/kevin/fs/test1_iptables ... 
and running afterwards make and make install, and then 

on the target machine (which access the fs by NFS) I run: 

iptables -t nat -A POSTROUTING -o ppp0 -j SNAT -s 10.1.1.25
The error I get is:

./iptables -A FORWARD -i eth1 -j SNAT
iptables v1.4.8: Couldn't load target `SNAT'
:/home/kevin/fs/test1_iptables/libexec/xtables/libipt_SNAT.so: cannot open
shared object file: No such file or directory


Of course I don't have /home/kevin/fs/ on the boards (this path is on the machine
on which I ran the cross compile).
I saw 
this post in gmane.comp.security.firewalls.netfilter.general.
http://comments.gmane.org/gmane.comp.security.firewalls.netfilter.general/40914

but it seems that the problem persists.

I tried also to work with DESTDIR and with other ideas from this post, but
nothing helped. 

What is the problem here, does anybody know ? I believe that cross compiling 
iptables and setting a path to xtables libs not to an absolute path 
is possible. Any ideas ?  


             reply	other threads:[~2012-04-16 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 15:19 Kevin Wilson [this message]
2012-04-16 15:59 ` How to install xtables extension to arbitrary path when cross compiling iptables? Jan Engelhardt
2012-04-17 12:58   ` Kevin Wilson
2012-04-17 13:04     ` Jan Engelhardt
2012-04-17 15:09       ` Sri Ram Vemulpali
2012-04-17 15:11         ` Jan Engelhardt

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=loom.20120416T170250-226@post.gmane.org \
    --to=wkevils@gmail.com \
    --cc=netfilter@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox