Description of problem: The current SOCI libraries (e.g., <= 3.0.0-21) are linked with the single-threaded version of the Boost libraries. Instead, they should be linked with the multi-threaded version of the Boost libraries. Version-Release number of selected component (if applicable): 3.0.0-21 How reproducible: Always Steps to Reproduce: 1. Install soci-core 2. Do, in a terminal: $ ldd /usr/lib64/libsoci_core.so.3.0.0 | grep boost 3. Watch the result Actual results: libboost_date_time.so.1.46.0 => /usr/lib64/libboost_date_time.so.1.46.0 libboost_program_options.so.1.46.0 => /usr/lib64/libboost_program_options.so.1.46.0 Expected results: libboost_date_time-mt.so.1.46.0 => /usr/lib64/libboost_date_time.so.1.46.0 libboost_program_options-mt.so.1.46.0 => /usr/lib64/libboost_program_options.so.1.46.0 Additional info: As almost all the other Boost-depending Fedora components rely on the multi-threaded version of the Boost libraries, linking with SOCI means coming with both versions of the Boost libraries. For instance, when the programs exit, the static variables are garbage-collected twice, meaning erratic core dumps.
soci-3.0.0-23.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/soci-3.0.0-23.fc15
soci-3.0.0-19.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/soci-3.0.0-19.fc14
Package soci-3.0.0-23.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing soci-3.0.0-23.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/soci-3.0.0-23.fc15 then log in and leave karma (feedback).
soci-3.0.0-19.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
soci-3.0.0-23.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.