Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Don't know how to compile tc
Date: Wed, 23 Jun 2004 21:38:01 +0000	[thread overview]
Message-ID: <200406232338.01369.stef.coene@docum.org> (raw)
In-Reply-To: <40D83C55.2010400@aircomp.aero>

On Wednesday 23 June 2004 16:12, L Rotger wrote:
> Stef Coene wrote:
> > I never had a problem compiling tc with 2.4 kernel sources.
> > Buy why do you want to recompile tc?
>
> Well, I like being able to compile things from source. Besides, I'm
> installing this on a production server and would like to rest assured
> that the binary I use is good. Call me paranoid.
>
> Could you send me the Makefile so I can compare with mine? Perhaps you
> have more software than it's in my workstation and you have libs or
> something I'm missing.
As far as I remember me, I downloaded the source and compiled it.
Can you post the compile errors?

> Also, what distro are you using and in case it is Debian, is it stable
> or development?
debian unstable.

Stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-06-23 21:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 14:04 [LARTC] Don't know how to compile tc L Rotger
2004-06-23 13:30 ` Stef Coene
2004-06-23 14:12 ` L Rotger
2004-06-23 14:51 ` Alessandro O. Ungaro
2004-06-23 16:05 ` L Rotger
2004-06-23 17:19 ` Jason Boxman
2004-06-23 21:38 ` Stef Coene [this message]
2004-06-24  8:00 ` L Rotger
2004-06-24 11:36 ` L Rotger

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=200406232338.01369.stef.coene@docum.org \
    --to=stef.coene@docum.org \
    --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