From: "Christoph A." <casmls@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
"Christoph A." <casmls@gmail.com>
Subject: Re: building nftables: ‘nfnl_nft_set_init’ undeclared
Date: Sun, 19 Jul 2009 18:32:11 +0200 [thread overview]
Message-ID: <4A634A8B.3040003@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0907181853420.4742@fbirervta.pbzchgretzou.qr>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
Am 18.07.2009 18:54, schrieb Jan Engelhardt:
> On Saturday 2009-07-18 13:54, Christoph A. wrote:
>> Hi!
>>
>> I'm building a enviroment where I can paly around with nftables.
>>
>> Building libnl-nft I encountered the same problem as described here:
>>
>> http://osdir.com/ml/general/2009-04/msg03933.html
>
> nfnl_nftset_init was removed in
> 0917b23733f46c65703545f82cc633836436f13b. nftables was not updated
> (yet).
>
> The combination of libnl-nft--9e3c81f64856ac0068f63f4d2b8f97c5f091e2e8 +
> nftables-414fa58ae9f283c35c8510fc31f28ba77bb5fdf5
> compiles through though.
After resolving the missing limits.h [1], the too new bison version [2]
and the configure script telling me that my malloc() version is not GNU
compatible, compiling was successfull.
[1] http://osdir.com/ml/catch/2009-03/msg04455.html
[2] http://markmail.org/message/xfay3mxmz4my4rog
thank you and thanks to orb (from #netfilter)
best regards
Christoph
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-07-19 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 11:54 building nftables: ‘nfnl_nft_set_init’ undeclared Christoph A.
2009-07-18 16:54 ` Jan Engelhardt
2009-07-19 16:32 ` Christoph A. [this message]
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=4A634A8B.3040003@gmail.com \
--to=casmls@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).