Issue 411 - DB_THREAD failures
Summary: DB_THREAD failures
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: build (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1999-12-27 02:47 UTC by hozer@drgw.net
Modified: 2014-08-01 21:05 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description hozer@drgw.net 1999-12-27 02:47:51 UTC 
Full_Name: Troy Benjegerdes
Version: 1.2.8
OS: Yellow Dog Linux (PPC)
URL: 
Submission from: (NULL) (165.90.142.42)


There is no mechanism to detect whether the DB_THREAD flag is supported on a
particular platform when using the db2 ldbm interface.

Sleepycat Berkeley db2 (provided with glibc-2.1.x) apparently requires
processor
specific ASM code for DB_THREAD to work. The result is that while a build on
PPC
successfully completes, slapd, ldif2ldbm, etc all report errors like:

ldif2ldbm: ldbm_db_errcall(): ==> illegal flag specified to db_appinit
ldif2ldbm: ldbm_initialize(): FATAL error in db_appinit() : Invalid argument

I suspect using an alternate --with-ldmb-api configure flag will fix this
problem,
but I do not know the best way to do this.
Comment 1 Kurt Zeilenga 2000-03-14 10:13:01 UTC 
changed notes
changed state Open to Suspended
moved from Incoming to Build
Comment 2 Kurt Zeilenga 2000-07-18 17:54:23 UTC 
changed notes
Comment 3 Kurt Zeilenga 2000-09-01 11:53:37 UTC 
changed state Suspended to Closed
Comment 4 OpenLDAP project 2014-08-01 21:05:08 UTC 
Implemented in devel, needs to be back ported to 1.2.