From: L Rotger <lrotger@aircomp.aero>
To: lartc@vger.kernel.org
Subject: [LARTC] Don't know how to compile tc
Date: Tue, 22 Jun 2004 14:04:05 +0000 [thread overview]
Message-ID: <40D83C55.2010400@aircomp.aero> (raw)
I am trying to build iproute2-2.4.7-20010824 from source on a 2.4.24
kernel. I have played a bit with ADDLIB and LDLIBS variables but I
always get errors so I suppose it's best if instead of playing I try to
understand what does the following mean (from the README file):
ADDLIB should contain inet_* functions, if your libc contains
obsolete resolver library (<4.9.4) and you have no correct libresolv.
ADDLIB should also contain dnet_* functions if you don't have a
libdnet with support for them. If your libdnet does have support,
then comment out that line and uncomment the line to add -ldnet to
LDLIBS.
So I have some questions as, for example, what means "ADDLIB should
contain inet_* functions"? and how do I know what is a correct libresolv
or if my libdnet has dnet_* support?. I can program in C and C++ in
Windows and love Linux but this paragraph goes over my head because I'm
not used to the environment. Someone told me to compile this if I was a
masochist so maybe others have encountered the same problem <g>
Thanks for your help.
L Rotger
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-06-22 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 14:04 L Rotger [this message]
2004-06-23 13:30 ` [LARTC] Don't know how to compile tc 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
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=40D83C55.2010400@aircomp.aero \
--to=lrotger@aircomp.aero \
--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