Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Iproute2
Date: Wed, 26 Dec 2001 11:01:31 +0000	[thread overview]
Message-ID: <marc-lartc-100936455428063@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100932369123736@msgid-missing>

On Tue, Dec 25, 2001 at 01:41:05AM +0200, Waters wrote:
> Hello,
> 
> There is a big need to shape traffic, and I heard that iproute2 could
> satisfy my needs, so I've downloaded lastest version, but seems there
> are problems, where is my mistake?
> 
> /usr/local/src/iproute2# make
> make[1]: Entering directory `/usr/local/src/iproute2/lib'
> gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -include ../include-glibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLVE_HOSTNAMES   -c -o ll_map.o ll_map.c
> gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -include ../include-glibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLVE_HOSTNAMES   -c -o libnetlink.o libnetlink.c
> ar rcs libnetlink.a ll_map.o libnetlink.o
> gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -include ../include-glibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLVE_HOSTNAMES   -c -o utils.o utils.c
> gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -include ../include-glibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLVE_HOSTNAMES   -c -o rt_names.o rt_names.c
> gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -include ../include-glibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLVE_HOSTNAMES   -c -o ll_types.o ll_types.c
> gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g -I../include-glibc -include ../include-glibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLVE_HOSTNAMES   -c -o ll_proto.o ll_proto.c
> ll_proto.c:36: `ETH_P_ECHO' undeclared here (not in a function)

Slackware will have an iproute package. This error probably means that it
can't find the right kernel sources.

Regards.

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  reply	other threads:[~2001-12-26 11:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-24 23:41 [LARTC] Iproute2 Waters
2001-12-26 11:01 ` bert hubert [this message]
2001-12-26 11:29 ` yangrunhua
2001-12-30  1:03 ` [LARTC] iproute2 Waters
2001-12-30  1:23 ` horape
2001-12-30 20:51 ` John Huttley
2001-12-30 20:57 ` Martin Petersen

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=marc-lartc-100936455428063@msgid-missing \
    --to=ahu@ds9a.nl \
    --cc=lartc@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