Berkeley DB is a programmatic toolkit that provides fast, reliable, scalable, and mission-critical database support in software ranging from applications running on hand-held appliances to enterprise-scale servers.
db3-3.2.9: description + notes
Berkeley DB includes highly concurrent B+tree, Hash, Fixed- and Variable-length record, and Persistent Queue access methods. Berkeley DB supports 256 TB databases and 4 GB key and data items. Berkeley DB provides complete transactional and database recovery support, online backups, and separate access to locking, logging and shared memory caching subsystems.
The Sleepycat Software Home Page has more information.
This product has been named db3 to indicate that (as compiled) it does not support a Berkeley DB 1.85 compatable API. It does however include the C++ API.
As requested on comp.sys.sgi.*, here is the configure options used to build this product.
./configure --prefix=/usr/freeware --enable-dynamic --disable-static --enable-cxx
NOTE: Developers intending to use this distribution for application development should be sure to read the information below. Users installing it for the runtime environment only need not read any further.
Developers intending to use this library for development of other freeware packages or their own software applications will need to be familiar with a few peculiarities due to the way that this library is packaged and installed. The reasons for this installation strategy are described further in the fw_common product release notes.
The header files and libraries in this package are installed into /usr/freeware. This means that when building software using this distribution you should be sure to do the following:
This flag will cause your compilations to correctly find the library's header files at compile time.
- Include the following flag on your compile lines:
- -I/usr/freeware/include
Include the following flag on your link lines:
-L/usr/freeware/lib32 (if using n32 ABI) This flag will cause the linker to correctly find the library's archive or shared object files at link time.
Additionally, include the following flag on your link lines:
-rpath /usr/freeware/lib32 (if using n32 ABI) This flag will allow the binary to locate the shared object library files when the application is run. This is required since the shared objects are stored in these /usr/freeware subdirectories which are not searched by the run-time linker by default.
Finally, if you are building an installable package for inst (contributing to freeware, for example) be sure to make your package depend upon this package. Add the following line to your spec file: prereq ( fw_db3.sw.lib 1270000000 1289999900 ) Following these guidelines will allow your application to safely and easily use the software in this package.
To auto-install this package, go back and click on the respective install icon.