Mailinglist Archive: opensuse-bugs (6630 mails)

< Previous Next >
[Bug 530069] New: A file (libboost_test_exec_monitor.a) which belongs to Boost.Test is missing from Boost packages
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 11 Aug 2009 10:00:46 -0600
  • Message-id: <bug-530069-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=530069


Summary: A file (libboost_test_exec_monitor.a) which belongs to
Boost.Test is missing from Boost packages
Classification: openSUSE
Product: openSUSE 11.2
Version: Factory
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Development
AssignedTo: pth@xxxxxxxxxx
ReportedBy: vlukas@xxxxxx
QAContact: qa@xxxxxxx
Found By: ---


User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux; x86_64; en_US)
KHTML/3.5.10 (like Gecko) SUSE

The Unit Testing Framework which belongs to the Boost libraries contains an
object file archive named libboost_test_exec_monitor.a. This file is missing
from the RPM packages provided by Opensuse (Factory).

In more detail, neither boost-devel nor libboost_test1_39_0 do contain the
mentioned file:
Executing "rpm -ql libboost_test1_39_0" gives
/usr/lib64/libboost_prg_exec_monitor.so.1.39.0
/usr/lib64/libboost_unit_test_framework.so.1.39.0

Executing "rpm -ql boost-devel | grep exec" gives
/usr/include/boost/iostreams/detail/execute.hpp
/usr/include/boost/python/exec.hpp
/usr/include/boost/test/execution_monitor.hpp
/usr/include/boost/test/impl/execution_monitor.ipp
/usr/include/boost/test/included/prg_exec_monitor.hpp
/usr/include/boost/test/included/test_exec_monitor.hpp
/usr/include/boost/test/prg_exec_monitor.hpp
/usr/include/boost/test/test_exec_monitor.hpp
/usr/lib64/libboost_prg_exec_monitor-mt.so
/usr/lib64/libboost_prg_exec_monitor.so
/usr/share/aclocal/ax_boost_test_exec_monitor.m4

"find /usr/lib64 -iname "*test_exec*"" also produces no output.

The full set of Boost RPMs is installed:
"rpm -qa | grep boost | sort" gives
boost-devel-1.39.0-1.1
boost-doc-1.39.0-1.1
boost-jam-3.1.17-1.14
boost-jam-debuginfo-3.1.17-1.3
boost-jam-debugsource-3.1.17-1.3
boost-license1_39_0-1.39.0-1.1
libboost_date_time1_39_0-1.39.0-1.1
libboost_filesystem1_39_0-1.39.0-1.1
libboost_graph1_39_0-1.39.0-1.1
libboost_iostreams1_39_0-1.39.0-1.1
libboost_math1_39_0-1.39.0-1.1
libboost_mpi1_39_0-1.39.0-1.1
libboost_program_options1_39_0-1.39.0-1.1
libboost_python1_39_0-1.39.0-1.1
libboost_regex1_39_0-1.39.0-1.1
libboost_serialization1_39_0-1.39.0-1.1
libboost_signals1_39_0-1.39.0-1.1
libboost_system1_39_0-1.39.0-1.1
libboost_test1_39_0-1.39.0-1.1
libboost_thread1_39_0-1.39.0-1.1
libboost_wave1_39_0-1.39.0-1.1

Building Boost 1.39 from scratch produces the mentioned object archive:
After executing
"bjam --build-dir=/home/lima/vanilla_sources/boost_1_39/obj_dir --layout=system
toolset=gcc stage" in the source directory, executing
"find boost_1_39_0/stage/lib/ -iname "*test_exec*"" gives
boost_1_39_0/stage/lib/libboost_test_exec_monitor.a

Please note that this report is not merely about a missing object archive
counterpart to a shared object. In fact, the original build of Boost only
produces the .a file, and no corresponding .so, as can be seen above.


Reproducible: Always

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
Follow Ups