All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dale Gallagher" <foobar@mighty.co.za>
To: lartc@vger.kernel.org
Subject: [LARTC] Solution: iproute2 and kernel 2.6.1
Date: Thu, 12 Feb 2004 15:17:49 +0000	[thread overview]
Message-ID: <web-233350815@mail01.infosat.net> (raw)

Thanks Toth

----- Toth Szabolcs wrote -----
> I have read on a mail list that you should install the
> db-4.1.25 Berkeley DB 4.1.25) get the
> iproute2-2.4.7-now-ss020116-try.tar.gz and patch which
> you need.

Woohoo!  Finally, an answer which just happened to point
me in the right direction.  Also, I spent a little more
time scouring through the compile errors.

The solution is in fact a mixed bag ;-)  The code uses
a hack to include db.h from a BerkeleyDB 3.x install. I
have BekeleyDB 4.1.25, so simply edited the Makefile
to reflect the difference!

File iproute2/include-glibc/db.h gives the hack away ;-)

----- <snip iproute2/include-glibc/db.h> -----
...

"The simplest trick which I was able to invent is to
write fake db.h including db_185.h and adding
-I/usr/include/db3 to CFLAGS."
...

#include <db_185.h>

----- </snip iproute2/include-glibc/db.h> -----

The solution was to chang the following line in
iproute2/Makefile from:

GLIBCFIX=-I../include-glibc -I/usr/include/db3

to:

GLIBCFIX=-I../include-glibc -I/usr/include/db4

and make sure that KERNEL_INCLUDE pointed to, which
I'd done from the very beginning.

> KERNEL_INCLUDE=/usr/src/linux-2.6.1/include

I'm one happy camper now *grin*

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

                 reply	other threads:[~2004-02-12 15:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=web-233350815@mail01.infosat.net \
    --to=foobar@mighty.co.za \
    --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.