All of lore.kernel.org
 help / color / mirror / Atom feed
From: aton <aton@packetdropped.org>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: libnfnetlink.h include generates problems...
Date: Mon, 11 Jun 2007 23:39:22 +0200	[thread overview]
Message-ID: <466DC10A.50805@packetdropped.org> (raw)

in one of my programs, i include the following two files:

#include <linux/netfilter.h>
#include <libnetfilter_queue/libnetfilter_queue.h>

while a few of my header files include each other i get errors from
these nfqueue header:

In file included from /usr/include/sys/uio.h:24,
                 from /usr/include/sys/socket.h:27,
                 from /usr/local/include/libnfnetlink/libnfnetlink.h:19,
                 from
/usr/local/include/libnetfilter_queue/libnetfilter_queue.h:16,
                 from misc.h:14,
                 from packeter.c:9:
/usr/include/sys/types.h:62: error: conflicting types for 'dev_t'
/usr/include/linux/types.h:27: error: previous declaration of 'dev_t'
was here
/usr/include/sys/types.h:72: error: conflicting types for 'mode_t'
/usr/include/linux/types.h:33: error: previous declaration of 'mode_t'
was here
/usr/include/sys/types.h:77: error: conflicting types for 'nlink_t'
/usr/include/linux/types.h:36: error: previous declaration of 'nlink_t'
was here
etc. etc.

i talked to some guys from ##c on freenode, and they said, probably
libnfnetlink.h should not directly include linux/types.h

sorry if this is my mistake, i am not very good at this stuff

greetings, aton

             reply	other threads:[~2007-06-11 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 21:39 aton [this message]
2007-06-11 22:07 ` [Patch 0/2] Re: libnfnetlink.h include generates problems Eric Leblond
2007-06-11 22:10   ` [Patch 1/2] " Eric Leblond
2007-06-13 18:51     ` Pablo Neira Ayuso
2007-06-11 22:11   ` [Patch 0/2] " Eric Leblond
2007-06-12 10:35 ` Pablo Neira Ayuso
2007-06-13  9:09   ` aton
2007-06-13  9:28     ` Pablo Neira Ayuso

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=466DC10A.50805@packetdropped.org \
    --to=aton@packetdropped.org \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.