On Apr 5, 2007, at 10:34 AM, Marcus Habermehl (BMH1980) wrote:
Internal or external Berkeley DB?
The external one from Oracle.
Same as rpm-4.4.7 uses internally.
What flags were used to build Berkeley DB?
../dist/configure --prefix=%{_prefix} --enable-compat185 --enable-cxx
rpm-4.4.2+ specifically turns on --enable-posixmutexes (which is
the default preferred locking scheme for db that is detected if
available iirc).
And the usual make and make install. _prefix is set to /usr. %
optflags are "-O2 -g -march=i686".
In %prep I'm applying two patches.
http://www.oracle.com/technology/products/berkeley-db/db/update/
2.5.20/patch.2.5.20.1
http://www.oracle.com/technology/products/berkeley-db/db/update/
2.5.20/patch.2.5.20.2
Same as rpm-4.4.8 uses internally. The only other patch applied to
Berkeley DB
is to handle robust posix mutexes. You don't necessarily need that
patch, lack of
it should not affect anything.
They are marked as required in the BLFS book.
Doing the following should either reproduce your rpm problem or
verify your
db build, depending on results:
cd /var/lib/rpm
db_verify Packages
73 de Jeff
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
