From: Pablo Neira Ayuso <pablo@netfilter.org>
To: t@tomdeb.org
Cc: netfilter@lists.netfilter.org
Subject: Re: conntrack-tools fails to compile
Date: Mon, 04 Jun 2007 16:12:31 +0200 [thread overview]
Message-ID: <46641DCF.10005@netfilter.org> (raw)
In-Reply-To: <20070602103248.62320224@snoopy>
t@tomdeb.org wrote:
> Hi,
>
> I am trying to compile conntrack-tools on centos5. After
> successfully built and installed rpms of libnfnetlink and
> libnetfilter_conntrack, I get the following error when making
> conntrack_tools:
>
> In file included from /usr/include/sys/uio.h:24,
> from /usr/include/sys/socket.h:27,
> from /usr/include/libnfnetlink/libnfnetlink.h:19,
> from proxy.c:19:
> /usr/include/sys/types.h:62: error: conflicting types for 'dev_t'
> /usr/include/linux/types.h:13: error: previous declaration of 'dev_t'
This problem was already fixed. Are you using lastest versions of
libnfnetlink and libnetfilter_conntrack?
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
prev parent reply other threads:[~2007-06-04 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 9:32 conntrack-tools fails to compile t
2007-06-04 14:12 ` 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=46641DCF.10005@netfilter.org \
--to=pablo@netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=t@tomdeb.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