From: "Sébastien Cramatte" <scramatte@zensoluciones.com>
To: netfilter@vger.kernel.org
Subject: Re: "extensions/libipt_ah.c" iptables 1.4.0 compilation problem
Date: Wed, 04 Jun 2008 00:51:05 +0200 [thread overview]
Message-ID: <4845CAD9.3090308@zensoluciones.com> (raw)
In-Reply-To: <4845C3C9.8000109@zensoluciones.com>
I answer to myself !
As you can see make include 2 paths to kernel include :
cc -O2 -Wall -Wunused -I"/lib/modules/2.6.16.19-xen/build"/include
-I../linux-2.6.24.7/include -
One is the correct, the same as KERNEL_DIR argument but the other match
KBUILD_OUTPUT default value.
To build my iptables I must specifiy 2 arguments :
#make KERNEL_DIR=../linux-2.6.24.7 KBUILD_OUTPUT=../linux-2.6.24.7
This is not "clearly" explained in the INSTALL doc file ...
Netfitler team just tell this ...
1) Next, make the package.
% make KERNEL_DIR=<<where-you-built-your-kernel>>
...
Please update the DOC !
Regards
Sébastien Cramatte escribió:
> Hello,
>
> I've patched my 2.6.24.7 kernel to use various netfilter extensions. I
> can compile and install it as a debian package.
> But I can't build "iptables 1.4.0" ... Extensions are detected but
> compilation hang on libipt_ah.c
>
> Note that I use a debian lenny
>
> #make KERNEL_DIR=../linux-2.6.24.7
> Extensions found: XT:geoip IPv4:ACCOUNT IPv4:IMQ IPv4:IPMARK
> IPv4:ROUTE IPv4:TARPIT IPv4:account IPv4:condition IPv4:ipp2p
> IPv4:ipv4options IPv4:layer7 IPv4:set IPv4:SET IPv6:IMQ IPv6:ROUTE
> cc -O2 -Wall -Wunused -I"/lib/modules/2.6.16.19-xen/build"/include
> -I../linux-2.6.24.7/include -Iinclude/ -DIPTABLES_VERSION=\"1.4.0\"
> -fPIC -o extensions/libipt_ah_sh.o -c extensions/libipt_ah.c
> In file included from include/iptables.h:4,
> from extensions/libipt_ah.c:8:
> include/xtables.h:84: warning: 'struct xt_entry_match' declared inside
> parameter list
> include/xtables.h:84: warning: its scope is only this definition or
> declaration, which is probably not what you want
> include/xtables.h:91: warning: 'struct xt_entry_match' declared inside
> parameter list
> include/xtables.h:99: warning: 'struct xt_entry_match' declared inside
> parameter list
> include/xtables.h:103: warning: 'struct xt_entry_match' declared
> inside parameter list
> include/xtables.h:140: warning: 'struct xt_entry_target' declared
> inside parameter list
> include/xtables.h:147: warning: 'struct xt_entry_target' declared
> inside parameter list
> include/xtables.h:154: warning: 'struct xt_entry_target' declared
> inside parameter list
> include/xtables.h:158: warning: 'struct xt_entry_target' declared
> inside parameter list
> extensions/libipt_ah.c: In function 'ah_init':
> extensions/libipt_ah.c:71: error: dereferencing pointer to incomplete
> type
> extensions/libipt_ah.c: In function 'ah_parse':
> extensions/libipt_ah.c:83: error: dereferencing pointer to incomplete
> type
> extensions/libipt_ah.c: In function 'ah_print':
> extensions/libipt_ah.c:128: error: dereferencing pointer to incomplete
> type
> extensions/libipt_ah.c: In function 'ah_save':
> extensions/libipt_ah.c:141: error: dereferencing pointer to incomplete
> type
> extensions/libipt_ah.c: At top level:
> extensions/libipt_ah.c:165: warning: initialization from incompatible
> pointer type
> extensions/libipt_ah.c:166: warning: initialization from incompatible
> pointer type
> extensions/libipt_ah.c:167: warning: initialization from incompatible
> pointer type
> extensions/libipt_ah.c:168: warning: initialization from incompatible
> pointer type
> make: *** [extensions/libipt_ah_sh.o] Error 1
>
> thank you for your help
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-03 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 22:20 "extensions/libipt_ah.c" iptables 1.4.0 compilation problem Sébastien Cramatte
2008-06-03 22:51 ` Sébastien Cramatte [this message]
2008-06-04 19:38 ` 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=4845CAD9.3090308@zensoluciones.com \
--to=scramatte@zensoluciones.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