From: Esteban Ribicic <eribicic@UolSinectis.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2 with new kernel
Date: Thu, 21 Nov 2002 14:02:02 +0000 [thread overview]
Message-ID: <marc-lartc-103788742620029@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103788251315201@msgid-missing>
from iproute2 tarball
How to compile this.
--------------------
1. Look at start of Makefile and set correct values for:
KERNEL_INCLUDE should point to correct linux kernel include directory.
blah blah blah
greets!
On Thu, 2002-11-21 at 10:47, Stef Coene wrote:
> On Thursday 21 November 2002 13:40, Tomas Bonnedahl wrote:
> > hello, is it necessary to recompile iproute2 when you add a new kernel, and
> > hence move the link /usr/src/linux to point on a different kernel?
> I'm not sure, but iproute uses some kernel files, so I think you better
> recompile.
>
> Stef
>
> --
>
> stef.coene@docum.org
> "Using Linux as bandwidth manager"
> http://www.docum.org/
> #lartc @ irc.oftc.net
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
--
Esteban Ribicic
Network Operation Center
UOL-Sinectis S.A.
Florida 537 Piso 6, Buenos Aires, Argentina
+54-11-4321-9110 ext 2503
+54-11-4321-9107 Directo
eribicic@uolsinectis.com
www.uolsinectis.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-21 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 12:40 [LARTC] iproute2 with new kernel Tomas Bonnedahl
2002-11-21 13:47 ` Stef Coene
2002-11-21 14:02 ` Esteban Ribicic [this message]
2002-11-21 14:20 ` Tomas Bonnedahl
2002-11-23 8:41 ` Ashok N N
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-103788742620029@msgid-missing \
--to=eribicic@uolsinectis.com \
--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