linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Largent <jlargent@imagelinks.com>
To: - Luis - <unix@amigo.net.gt>
Cc: linux <linux-admin@vger.kernel.org>
Subject: Re: openldap
Date: Thu, 07 Aug 2003 15:39:55 -0400	[thread overview]
Message-ID: <3F32AB0B.2060000@imagelinks.com> (raw)
In-Reply-To: <1060275269.28177.18.camel@luisvalencia>

db4 is the default for Redhat 9, openldap is looking for db3.

You should be able to install the db3 packages on you rh9 box.
db3-3.3.11-6
db3-devel-3.3.11-6
db3-utils-3.3.11-6


- Luis - wrote:
> hi, im trying to install openldap 2.0.9 in a RH9 box, but when i make
> configure --enable-shell i got the following error.
> 
> checking for pthread.h... yes
> checking POSIX thread version... final
> checking for LinuxThreads pthread.h... yes
> checking for GNU Pth pthread.h... no
> checking for sched.h... yes
> checking for pthread_create in default libraries... no
> checking for pthread link with -kthread... no
> checking for pthread link with -pthread... no
> checking for pthread link with -pthreads... no
> checking for pthread link with -mthreads... no
> checking for pthread link with -thread... no
> checking for pthread link with -lpthread -lmach -lexc -lc_r... no
> checking for pthread link with -lpthread -lmach -lexc... no
> checking for pthread link with -lpthread -Wl,-woff,85... no
> checking for pthread link with -lpthread... no
> checking for pthread link with -lc_r... no
> checking for pthread link with -threads... no
> checking for pthread link with -lpthreads -lmach -lexc -lc_r... no
> checking for pthread link with -lpthreads -lmach -lexc... no
> checking for pthread link with -lpthreads -lexc... no
> checking for pthread link with -lpthreads... no
> configure: error: could not link with POSIX Threads
> 
> i also try with a newer version of openldap 2.1.22 but with this one i
> got the following, 
> 
> checking for db.h... yes
> checking for Berkeley DB link (default)... no
> checking for Berkeley DB link (-ldb41)... no
> checking for Berkeley DB link (-ldb-41)... no
> checking for Berkeley DB link (-ldb-4.1)... no
> checking for Berkeley DB link (-ldb-4-1)... no
> checking for Berkeley DB link (-ldb-4)... no
> checking for Berkeley DB link (-ldb4)... no
> checking for Berkeley DB link (-ldb)... yes
> checking for Berkeley DB thread support... yes
> checking Berkeley DB version for BDB backend... no
> configure: error: BDB: BerkeleyDB version incompatible
> 
> i need back shell support because im going to use it for a netmeeting
> server.
> 
> Can anybody give a light here please.
> 

-- 
Jeff Largent                   ImageLinks, Inc.
Sr System Admin                Melbourne, Fl 32935
(321) 253-0011                 fax: (321) 253-5559


  reply	other threads:[~2003-08-07 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 16:54 openldap - Luis -
2003-08-07 19:39 ` Jeff Largent [this message]
     [not found] <B6DFCBE338DE6741A24ECEA890730A19642BAE@exchtwo>
2003-08-08 15:07 ` openldap - Luis -

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=3F32AB0B.2060000@imagelinks.com \
    --to=jlargent@imagelinks.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=unix@amigo.net.gt \
    /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;
as well as URLs for NNTP newsgroup(s).