Bug 240047 - Can't rebuild with db4-devel installed
Summary: Can't rebuild with db4-devel installed
Alias: None
Product: Fedora
Classification: Fedora
Component: cyrus-sasl   
(Show other bugs)
Version: 7
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Steve Conklin
QA Contact: Brian Brock
Keywords: Reopened
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-14 17:23 UTC by Derek Atkins
Modified: 2008-06-17 01:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-17 01:19:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Derek Atkins 2007-05-14 17:23:48 UTC
Description of problem:

I was trying to rebuild cyrus-sasl and it fails if db4-devel is installed.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. install the cyrus-sasl SRPM on a fully-updated F7t4 machine
2. rpmbuild -bb cyrus-sasl.spec
3. watch the build fail.
Actual results:

gcc -Wall -W -I/usr/kerberos/include -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
-mtune=generic -fasynchronous-unwind-tables -fPIC -I/usr/include/mysql -g -pipe
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4
-m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables
-fno-strict-aliasing -fwrapv -o .libs/dbconverter-2 dbconverter-2.o 
-L/usr/kerberos/lib -L/usr/lib/mysql -L/usr/lib ../sasldb/.libs/libsasldb.a
../lib/.libs/libsasl2.so -ldl
-L/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/db-instroot/lib -ldb -lresolv -lcrypt 
dbconverter-2.o: In function `berkeleydb_open':
/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/utils/dbconverter-2.c:214: undefined
reference to `db_create_cyrus_sasl_sasldb_rh'
dbconverter-2.o: In function `berkeleydb_close':
/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/utils/dbconverter-2.c:249: undefined
reference to `db_strerror_cyrus_sasl_sasldb_rh'
dbconverter-2.o: In function `listusers':
/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/utils/dbconverter-2.c:277: undefined
reference to `db_strerror_cyrus_sasl_sasldb_rh'
../sasldb/.libs/libsasldb.a(db_berkeley.o): In function `berkeleydb_close':
/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/sasldb/db_berkeley.c:147: undefined
reference to `db_strerror_cyrus_sasl_sasldb_rh'
../sasldb/.libs/libsasldb.a(db_berkeley.o): In function `berkeleydb_open':
/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/sasldb/db_berkeley.c:100: undefined
reference to `db_create_cyrus_sasl_sasldb_rh'
/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/sasldb/db_berkeley.c:117: undefined
reference to `db_strerror_cyrus_sasl_sasldb_rh'
../sasldb/.libs/libsasldb.a(db_berkeley.o): In function `_sasldb_putdata':
/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/sasldb/db_berkeley.c:318: undefined
reference to `db_strerror_cyrus_sasl_sasldb_rh'
/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/sasldb/db_berkeley.c:330: undefined
reference to `db_strerror_cyrus_sasl_sasldb_rh'
../sasldb/.libs/libsasldb.a(db_berkeley.o): In function `_sasldb_getdata':
/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/sasldb/db_berkeley.c:228: undefined
reference to `db_strerror_cyrus_sasl_sasldb_rh'
collect2: ld returned 1 exit status
make[2]: *** [dbconverter-2] Error 1
make[2]: Leaving directory `/usr/src/redhat/BUILD/cyrus-sasl-2.1.22/utils'

Expected results:

A completed build

Additional info:

rpm -e db4-devel fixes the problem and lets me rebuild cyrus-sasl.

Comment 1 Steve Conklin 2008-02-28 21:14:33 UTC
I can't reproduce this on Fedora 7, 8, or devel

Comment 2 Derek Atkins 2008-04-09 05:21:08 UTC
I just reproduced it on Fedora 7.  Same issue as before.  I did:

rpm -ivh cyrus-sasl-2.1.22-8.fc7.src.rpm
cd /usr/src/redhat/SPECS
rpmbuild -bb cyrus-sasl.spec

And it gave the exact same output as above.  Then I do:

rpm -e db4-devel

And then re-run the rpmbuild and it works.  It's POSSIBLE that this is related
to the changes suggested in bug #240051 but I really doubt it.

But this DOES happen on my (up to date) Fedora 7 machine.  I don't know why you
cannot reproduce it but I'm certainly happy to help figure it out.  What
information do you want/need?  I can provide:
1) a full build log
2) full output of rpm -qa
3) most anything else you need me to lookup for you.

I still consider this low priority because it's easy to work around...  But it
would be nice to figure out why this is happening.

Comment 3 Bug Zapper 2008-05-14 12:14:08 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2008-06-17 01:19:10 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.