From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: conntrack/libnetfilter_conntrack build warnings/errors
Date: Sun, 09 Dec 2007 18:25:22 +0100 [thread overview]
Message-ID: <475C2502.5090703@netfilter.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0712091318110.17491@fbirervta.pbzchgretzou.qr>
Hi Jan,
Jan Engelhardt wrote:
> CC deprecated.lo
> deprecated.c: In function 'nfct_sprintf_conntrack':
> deprecated.c:567: warning: 'nfct_sprintf_protocol' is deprecated (declared at deprecated.c:492)
> deprecated.c:570: warning: 'nfct_sprintf_timeout' is deprecated (declared at deprecated.c:500)
> [...]
These warnings are supposed to be normal, I moved the old
libnetfilter_conntrack API to the file deprecated.c and added the
deprecated attribute to warn people that they are using a deprecated
API. Thus, whoever using very old conntrack-tools versions or using the
old API may move to new versions of the tools or use the new API. I'm
thinking about removing the old libnetfilter_conntrack API in 6 months.
> CCLD conntrack_events
> make[1]: *** No rule to make target `conntrack_master.o', needed by `conntrack_master'. Stop.
> make[1]: Leaving directory `/usr/src/packages/BUILD/netfilter-tools-0.svn7135/libnetfilter_conntrack/utils'
> make: *** [all-recursive] Error 1
> error: Bad exit status from /var/tmp/rpm-tmp.7694 (%build)
I forgot to commit utils/conntrack_master.c to SVN. Now it's fixed. Thanks.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2007-12-09 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 12:19 conntrack/libnetfilter_conntrack build warnings/errors Jan Engelhardt
2007-12-09 17:25 ` Pablo Neira Ayuso [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=475C2502.5090703@netfilter.org \
--to=pablo@netfilter.org \
--cc=jengelh@computergmbh.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).