View previous topic :: View next topic |
Author |
Message |
rchan00 n00b
Joined: 30 Jun 2004 Posts: 29
|
Posted: Fri Oct 01, 2004 3:04 pm Post subject: How to emerge db(uniquename) and then OpenLDAP? |
|
|
Folks,
How did you emerge db4 (4.1.25) and then OpenLDAP?
When I tried that db4 is created with configure ... --uniquename
in the ebuild. This means that the function db_version is
called db_version_4001.
When emerging OpenLDAP it looks for db_version thus the configure
fails.
Any pointers?
a) Disable --uniquename in the db ebuild configure? Why is it there
in the first place?
b) ?????? |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Tue Oct 05, 2004 4:16 am Post subject: |
|
|
What versions of sys-libs/db do you currently have installed? |
|
Back to top |
|
|
jaspal kallar Apprentice
Joined: 25 Feb 2004 Posts: 194 Location: Sweden
|
Posted: Tue Oct 05, 2004 1:09 pm Post subject: |
|
|
I think I have a simlar problem. When I do:
Code: | emerge -uD world
Calculating world dependencies ...done!
>>> emerge (1 of 1) net-nds/openldap-2.1.30-r2 to /
>>> md5 src_uri ;-) openldap-2.1.30.tgz
>>> Unpacking source...
>>> Unpacking openldap-2.1.30.tgz to /var/tmp/portage/openldap-2.1.30-r2/work
* Applying openldap-2.1.30-db40.patch... [ ok ]
* Applying openldap-2.1.27-perlthreadsfix.patch... [ ok ]
* Applying openldap-2.1.30-ximian_connector.patch... [ ok ]
configure.in:2337: warning: AC_TRY_RUN called without default to allow cross compiling
>>> Source unpacked.
berkdb
* Using Berkeley DB for local backend
Copyright 1998-2004 The OpenLDAP Foundation, All Rights Reserved.
Restrictions apply, see COPYRIGHT and LICENSE files.
Configuring OpenLDAP 2.1.30-Release ...
[snip]
.
.
.
checking for Berkeley DB thread support... yes
checking Berkeley DB version for BDB backend... no
configure: error: BDB: BerkeleyDB version incompatible
!!! ERROR: net-nds/openldap-2.1.30-r2 failed.
!!! Function econf, Line 362, Exitcode 1
!!! econf failed
|
Code: | emerge -p sys-libs/db
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] sys-libs/db-4.1.25_p1-r3
|
Any pointers on what to do?
Infact I don't know why I need openldap. How can I check which other packages are dependent on openldap in the case that I want to remove it altogether ? |
|
Back to top |
|
|
rchan00 n00b
Joined: 30 Jun 2004 Posts: 29
|
Posted: Tue Oct 05, 2004 1:34 pm Post subject: |
|
|
My original db was also 4.1.25_r3 from an emerge world (after
using a Stage 3 tarball) - this was before trying to install
OpenLDAP.
The problem arises from trying to install OpenLDAP on top
of a basic system (all the usual stuff emerge'd and running
well).
Checked out 4.2 ebuild -- that has --uniquename in the configure too.
For a test I re-emerged db 4 disabling --uniquename and was
able to install OpenLDAP - now I'm not sure what I have broken! |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Wed Oct 06, 2004 11:35 am Post subject: |
|
|
Try installing a version of db-4.0.x. If you are not using ACCEPT_KEYWORDS, you'll want db-4.0.14-r2. If you're a bit unfamiliary with how to emerge particular versions of a package, use the command;
Code: | emerge -v =db-4.0.14-r2 |
|
|
Back to top |
|
|
|