All of lore.kernel.org
 help / color / mirror / Atom feed
From: go0ogl3 <go0ogl3@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2 compilation problem
Date: Wed, 02 Feb 2005 15:34:05 +0000	[thread overview]
Message-ID: <a3558a98050202073477f482f1@mail.gmail.com> (raw)
In-Reply-To: <18dc01c50922$3b467b20$6e69690a@RIMAS>

On Wed, 2 Feb 2005 15:11:34 -0000, Remus <rmocius@auste.elnet.lt> wrote:
> Gypsy,
> 
> I was missing only db31-3-1-17-i486-1, but after it install I still
> get the same errors.
> 
> Regards
> 
> Remus
> 
> 
> > Remus wrote:
> >>
> >> Hi folks,
> >>
> >> I just tried to compile the latest (current) iproute2 and got these
> >> errors:
> >>
> >> arpd.c:19:20: db_185.h: No such file or directory
> > =SNIP=
> >> make[1]: *** [arpd] Error 1
> >> make[1]: Leaving directory
> >> `/home/iproute2/new/Source/Orig/iproute2-050124/misc'
> >> make: *** [all] Error 2
> >>
> >> My kernel 2.6.10 on Slackware 10 (current)
> >>
> >> Any ideas?
> >>
> >> Regards
> >>
> >> Remus
> >
> > Install from slackware/l the db3-3.11-i486-4 db31-3-1-17-i486-1 and
> > db4-4.2.52-i486-2 libraries.
> >
> > gypsy
> >
> >
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 

Just edit your Makefile where you find a line like this:

--- cut here ---
# Path to db_185.h include
DBM_INCLUDE:=/usr/include
--- and here ---

with:

#Path to db_185.h include
DBM_INCLUDE:=/usr/include/db4/db_185.h

Compile and you'll be fine :)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2005-02-02 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 12:25 [LARTC] iproute2 compilation problem Remus
2005-02-02 14:58 ` gypsy
2005-02-02 15:11 ` Remus
2005-02-02 15:34 ` go0ogl3 [this message]
2005-02-02 15:57 ` Remus

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=a3558a98050202073477f482f1@mail.gmail.com \
    --to=go0ogl3@gmail.com \
    --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.