All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radosław Łoboda" <p0wer@tl.krakow.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Compile problems...
Date: Fri, 06 Sep 2002 13:53:10 +0000	[thread overview]
Message-ID: <marc-lartc-103132013228784@msgid-missing> (raw)


Hi.

I have some problems while applying WRR, ESFQ and HTB3 patches and then
compiling kernel. The HTB patch rejects some lines. I haven't tried to
change the order of the patches but I suppose it won't work anyway. On
2.4.18 i tried HTB3 and ESFQ and it compiled fine...

The other thing is that after compiling the 2.4.18 with ESFQ I need to
recompile the iproute package. There are also some problems with it. Even
without patches, it wont compile. Here are the errors:

ll_proto.c:36: `ETH_P_ECHO' undeclared here (not in a function)
ll_proto.c:36: Initializer element is not constant
ll_proto.c:36: (near initialization for `llproto_names[1].id')

There are probably some inckudes missing, but i don;t know which ones ! I
searches thorugh package database and installed almost all net-related
-dev libraries. Please help me and tell me which libraries are needed.

I use Debian Woody.

-- 

##########################################
#           |       p0wer        |       #
#   __      |    GG#1877248      |       #
#  (oo)     | p0wer@bojko.eu.org |       #
# / \/ \ Go away or I will replace you   #
# `V__V' with a very small shell script. #
##########################################



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

             reply	other threads:[~2002-09-06 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 13:53 Radosław Łoboda [this message]
2002-09-06 14:46 ` [LARTC] Compile problems lhyuan
2002-09-06 20:56 ` Jose Luis Domingo Lopez
2002-09-08 19:22 ` Radosław Łoboda

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-103132013228784@msgid-missing \
    --to=p0wer@tl.krakow.pl \
    --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 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.