From: Fabrice <fabricedeyber@agilemesh.com>
To: netfilter@vger.kernel.org
Subject: Re: how to install xtables extension to arbitrary path?
Date: Mon, 14 Feb 2011 14:25:33 +0000 (UTC) [thread overview]
Message-ID: <loom.20110214T152123-163@post.gmane.org> (raw)
In-Reply-To: 4CB712C3.3030804@21com.com
Xing Qianqian <xingqq <at> 21com.com> writes:
>
> Hi,
>
> When building iptables, we can use "configure" to specify the xtables
> extension install path by "prefix" or "withxtlibdir". And when we
> running the iptables, iptables seems to search for the xtables extension
> libraries only in the path that was specified by "configure". If we move
> the xtables extension libraries to some other place, iptables will
> report failing to load the "so" files.
>
> Because I'm doing cross compiling, and I will place the xtables
> extension libraries in the target board, and the final path might be
> different than the "configure" path. Do you know how to make iptables to
> load the correct xtables extensions?
>
> Thanks.
>
Hi Xing,
I'm having the same issue. I'm able to cross compile but when I install
to another file system the libraries always look at the absolute path which
is not valid anymore. How did you get around the issue?
next prev parent reply other threads:[~2011-02-14 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 14:25 how to install xtables extension to arbitrary path? Xing Qianqian
2010-10-14 15:40 ` Jan Engelhardt
2011-02-14 14:25 ` Fabrice [this message]
2011-02-14 14:43 ` Mr Dash Four
2011-02-14 14:50 ` Jan Engelhardt
2011-02-14 14:55 ` Mr Dash Four
2011-02-14 15:03 ` Fabrice
2011-02-14 15:20 ` Jan Engelhardt
2011-02-14 15:25 ` Fabrice
2011-02-14 15:43 ` Jan Engelhardt
2011-02-14 16:19 ` Fabrice
2011-02-14 17:43 ` Fabrice
2011-02-14 22:53 ` 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.20110214T152123-163@post.gmane.org \
--to=fabricedeyber@agilemesh.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