From: Justin Owens <justin@commtech.ie>
To: lartc@vger.kernel.org
Subject: [LARTC] Install Question
Date: Thu, 16 May 2002 11:09:55 +0000 [thread overview]
Message-ID: <marc-lartc-102154899110751@msgid-missing> (raw)
Sorry for asking such basic questions but I haven't used iproute or htb
before.
I am using RedHat 7.1 (2.4 kernel) and I want to use HTB3.3 and
iproute2-2.4.7
Before I make and install iproute do I need to do something with the HTB
files...I can't find any docs on this
Would appreciate it if someone could give me a few pointers, or point me to
a doc...there's very little in the LARC Howto.
Thanks in advance
Justin Owens
-----Original Message-----
From: Herman Cremer [mailto:admin@help.co.za]
Sent: 15 May 2002 07:58
To: Martin Devera; Anton Yurchenko
Cc: lartc@mailman.ds9a.nl
Subject: RE: [Fwd: Re: [LARTC] borrowing only from parent]
Question :
> > Has anyone ever managed to compile iproute2 from source,
> > running a 2.4.x kernel ?
I have also managed to solve it in another way..
Here is how ...
Solution 1:
Well I have managed to fix the compile error on a kernel 2.4.x
If we have a look at the file, /usr/src/linux/include/linux/if_ether.h
that you get from the different kernels, we notice a change.
On 2.2.x kernel...
#define ETH_P_ECHO 0x0200 /* Ethernet Echo packet */
On 2.4.x kernel...
#define ETH_P_PUP 0x0200 /* Xerox PUP packet */
Q: How to fix it ?
In the directory /lib of the source from the iproute2 tarball,
is a file called, 'll_proto.c'
In the file, there is an entry '__PF(ECHO,echo)' on line 36.
A: Remove this line, and try to compile it again.
Solution 2:
> Using SGL :)
>
> hvisage@meklon:~$ tar -zxf
> download/iproute2-2.4.7-now-ss020116-try.tar.gz
> hvisage@meklon:~$ cd iproute2/
> hvisage@meklon:~/iproute2$ sed -e "s/UTILS_H/IPROUTE2_UTILS_H/g"
> < include/utils.h > include/iproute2_utils.h
> hvisage@meklon:~/iproute2$ for i in `find . -type f | xargs grep
> utils.h|grep :|cut -f 1 -d :`; do sed -e
> 's/"utils.h"/"iproute2_utils.h"/' <$i > $i.new;mv $i.new $i;done
> hvisage@meklon:~/iproute2$ make
>
> QED ;^)
>
> The reason:
> there are a /usr/include/utils.h that get's included before
> the iproute2/include/utils.h :(
----
To unsubscribe from this list: send the line "unsubscribe glug" in
the subject of a message to glug-request@linux.org.za. If you have a
problem unsubscribing, please mail glug-admins@linux.org.za
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
The information contained in this email is privileged and confidential, intended only for the use of the individual or entity to whom it is addressed. If the reader of this email is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender immediately by email and delete this email. Any views expressed in this email are those of the individual sender unless the sender specifically states
This mail was virus scanned by SurfControl.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-05-16 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 11:09 Justin Owens [this message]
2002-05-16 11:52 ` [LARTC] Install Question Stef Coene
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-102154899110751@msgid-missing \
--to=justin@commtech.ie \
--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