From: Amin Azez <azez@ufomechanic.net>
To: netfilter-devel@lists.netfilter.org
Subject: Re: Problem with compiling libnfnetlink
Date: Thu, 20 Apr 2006 10:55:09 +0100 [thread overview]
Message-ID: <44475A7D.6020305@ufomechanic.net> (raw)
In-Reply-To: <859616420604190401u11748b19r12b18558036c2afe@mail.gmail.com>
If I recall correctly this is beause you specified a wrong path to your
kernel source and so netlink.h was included from /usr/include/linux
instead of from your kernel source.
I'm possibly not the only one troubled by the existance of
/usr/include/linux, to me the whole thing smacks of presumtion and trouble.
You might want to:
find /path/to/kernel/src -name netlink.h
and see if there is even one there.
It would be helpful if you could include the output of gcc when
compiling (not linking) so we can check the -I paths to see what kernel
path it is including.
Sam
David Vogt wrote:
> Hi,
>
> I downloaded the latest version of libnfnetlink from the subversion
> trunk (revison 6582 that is), after running "./autogen.sh" and
> "./configure --with-kernel=<PATH_TO_KERNEL_SRC>" (both of which seem
> to work fine), "make" outputs
>
> Making all in src
> make[1]: Entering directory `/home/david/netfilter.org/libnfnetlink/src'
> if /bin/sh ../libtool --mode=compile gcc -DPACKAGE_NAME=\"\"
> -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\"
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"libnfnetlink\"
> -DVERSION=\"0.0.16\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -I. -I.
> -I../include -fPIC -Wall -g -O2 -MT libnfnetlink.lo -MD -MP -MF
> ".deps/libnfnetlink.Tpo" \
> -c -o libnfnetlink.lo `test -f 'libnfnetlink.c' || echo './'`libnfnetlink.c; \
> then mv -f ".deps/libnfnetlink.Tpo" ".deps/libnfnetlink.Plo"; \
> else rm -f ".deps/libnfnetlink.Tpo"; exit 1; \
> fi
> mkdir .libs
> gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\"
> -DPACKAGE=\"libnfnetlink\" -DVERSION=\"0.0.16\" -DSTDC_HEADERS=1
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
> -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
> -DHAVE_DLFCN_H=1 -I. -I. -I../include -fPIC -Wall -g -O2 -MT
> libnfnetlink.lo -MD -MP -MF .deps/libnfnetlink.Tpo -c libnfnetlink.c
> -fPIC -DPIC -o .libs/libnfnetlink.o
> In file included from libnfnetlink.c:40:
> /usr/include/linux/netlink.h:22: error: syntax error before "__u32"
> /usr/include/linux/netlink.h:28: error: syntax error before "__u32"
> /usr/include/linux/netlink.h:30: error: syntax error before "nlmsg_flags"
> /usr/include/linux/netlink.h:31: error: syntax error before "nlmsg_seq"
> /usr/include/linux/netlink.h:32: error: syntax error before "nlmsg_pid"
> /usr/include/linux/netlink.h:82: error: field `msg' has incomplete type
>
> The kernel I use is 2.6.16. I've never built libnfnetlink from source,
> so I am pretty sure I missed an important step. Any help would be
> great.
>
> David
>
>
next prev parent reply other threads:[~2006-04-20 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 11:01 Problem with compiling libnfnetlink David Vogt
2006-04-20 9:55 ` Amin Azez [this message]
2006-04-20 11:05 ` David Vogt
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=44475A7D.6020305@ufomechanic.net \
--to=azez@ufomechanic.net \
--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.