From: Nadia Derbey <Nadia.Derbey@bull.net>
To: netdev@vger.kernel.org
Subject: [IPROUTE] compilation problem
Date: Thu, 15 Mar 2007 13:55:36 +0100 [thread overview]
Message-ID: <45F94248.4080003@bull.net> (raw)
Hi,
Trying to compile iproute2 (downloaded from
http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.20-070313.tar.gz)
I get the following error message.
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include
-DRESOLVE_HOSTNAMES -DCONFIG_GACT -DCONFIG_GACT_PROB -c -o m_ipt.o m_ipt.c
In file included from ../include/libiptc/libiptc.h:6,
from ../include/iptables.h:5,
from m_ipt.c:17:
../include/linux/netfilter_ipv4/ip_tables.h:115:39: error:
linux/netfilter/xt_tcpudp.h: No such file or directory
make[1]: *** [m_ipt.o] Error 1
rm emp_ematch.lex.c emp_ematch.yacc.c
make[1]: Leaving directory `/home/lkernel/src/iproute-2.6.20-070313/tc'
This error goes away when I copy xt_tcpudp.h from the linux kernel tree
(include/linux/netfilter) to the the private iproute include directory.
Am I doing something wrong?
Please Cc me since I'm not subscribed.
Regards,
Nadia
next reply other threads:[~2007-03-15 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 12:55 Nadia Derbey [this message]
2007-03-16 18:23 ` [IPROUTE] compilation problem Stephen Hemminger
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=45F94248.4080003@bull.net \
--to=nadia.derbey@bull.net \
--cc=netdev@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).