From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Subject: Re: iproute2 issue with adding rules.
Date: Mon, 17 May 2010 13:13:06 -0700 [thread overview]
Message-ID: <4BF1A352.5020500@candelatech.com> (raw)
In-Reply-To: <4BF192F9.8000008@candelatech.com>
On 05/17/2010 12:03 PM, Ben Greear wrote:
> On older releases, you can do this with iproute:
>
> # ip ru add from 9.9.9.2/32 table 226 pref 400
> #
>
> But, in latest git, it returns an error:
> # ip ru add from 9.9.9.2/32 table 226 pref 400
> Error: an inet prefix is expected rather than "9.9.9.2/32".
>
> Is that on purpose?
I was thinking maybe this was a library issue, since I compiled
on one machine and ran the 'ip' exe on another. So, I tried compiling
on the test system.
But, iproute will not compile, apparently because it finds the
/usr/include/linux header files before whatever is packaged with
iproute:
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include -DRESOLVE_HOSTNAMES -DLIBDIR=\"/usr/lib/\" -c -o ipaddress.o ipaddress.c
ipaddress.c: In function ‘print_linkinfo’:
ipaddress.c:334: error: ‘IFLA_VFINFO’ undeclared (first use in this function)
ipaddress.c:334: error: (Each undeclared identifier is reported only once
ipaddress.c:334: error: for each function it appears in.)
make[1]: *** [ipaddress.o] Error 1
make[1]: Leaving directory `/root/git/iproute2/ip'
make: *** [all] Error 2
I tried moving /usr/include/linux out of the way, but then it blows up
even worse (can't find errno.h, etc)
Are we supposed to be able to compile iproute2 on a system with moderately
outdated kernel headers?
If not, why bother with the iproute/include/linux directory at all?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-05-17 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 19:03 iproute2 issue with adding rules Ben Greear
2010-05-17 20:13 ` Ben Greear [this message]
2010-05-17 20:27 ` Stephen Hemminger
2010-05-17 20:28 ` Ben Greear
2010-05-17 20:30 ` Chris Wright
2010-05-17 20:34 ` Ben Greear
2010-05-17 21:41 ` 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=4BF1A352.5020500@candelatech.com \
--to=greearb@candelatech.com \
--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 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.