Mailinglist Archive: opensuse-bugs (4251 mails)

< Previous Next >
[Bug 1038083] New: error: ‘make_array’ is not a member of ‘boost::serialization’
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 08 May 2017 16:21:50 +0000
  • Message-id: <bug-1038083-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1038083


Bug ID: 1038083
Summary: error: ‘make_array’ is not a member of
‘boost::serialization’
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Development
Assignee: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
Reporter: ingham@xxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

A recent tumbleweed update appears to have broken part of boost. Two weeks
ago, things were compiling fine.

This example
[code]
#include <boost/numeric/ublas/triangular.hpp>
#include <boost/numeric/ublas/io.hpp>

int main () {
using namespace boost::numeric::ublas;
matrix<double> m (3, 3);
triangular_adaptor<matrix<double>, lower> tal (m);
for (unsigned i = 0; i < tal.size1 (); ++ i)
for (unsigned j = 0; j <= i; ++ j)
tal (i, j) = 3 * i + j;
std::cout << tal << std::endl;
triangular_adaptor<matrix<double>, upper> tau (m);
for (unsigned i = 0; i < tau.size1 (); ++ i)
for (unsigned j = i; j < tau.size2 (); ++ j)
tau (i, j) = 3 * i + j;
std::cout << tau << std::endl;
}
[/code]
Which is copied from the boost example here:
http://www.boost.org/doc/libs/1_36_0/libs/numeric/ublas/doc/triangular.htm
fails:
[code]
$ g++ foo.cpp
In file included from /usr/include/boost/numeric/ublas/vector.hpp:21:0,
from /usr/include/boost/numeric/ublas/matrix.hpp:18,
from /usr/include/boost/numeric/ublas/triangular.hpp:16,
from foo.cpp:1:
/usr/include/boost/numeric/ublas/storage.hpp: In member function ‘void
boost::numeric::ublas::unbounded_array<T, ALLOC>::serialize(Archive&, unsigned
int)’:
/usr/include/boost/numeric/ublas/storage.hpp:299:18: error: ‘make_array’ is
not
a member of ‘boost::serialization’
ar & serialization::make_array(data_, s);
^~~~~~~~~~~~~
/usr/include/boost/numeric/ublas/storage.hpp: In member function ‘void
boost::numeric::ublas::bounded_array<T, N, ALLOC>::serialize(Archive&, unsigned
int)’:
/usr/include/boost/numeric/ublas/storage.hpp:494:18: error: ‘make_array’ is
not
a member of ‘boost::serialization’
ar & serialization::make_array(data_, s);
^~~~~~~~~~~~~
In file included from /usr/include/boost/numeric/ublas/triangular.hpp:16:0,
from foo.cpp:1:
/usr/include/boost/numeric/ublas/matrix.hpp: In member function ‘void
boost::numeric::ublas::c_matrix<T, M, N>::serialize(Archive&, unsigned int)’:
/usr/include/boost/numeric/ublas/matrix.hpp:5977:18: error: ‘make_array’ is
not
a member of ‘boost::serialization’
ar & serialization::make_array(data_, N);
^~~~~~~~~~~~~
[/code]
This problem appears to be discussed and fixed in this boost bug:
https://svn.boost.org/trac/boost/ticket/12516

Other possibly relevant data:
$ rpm -qa '*boost*' '*c++*' | sort
boost_1_64-devel-1.64.0-1.1.x86_64
boost-license1_64_0-1.64.0-1.1.noarch
gcc6-c++-6.3.1+r245113-1.5.x86_64
gcc-c++-6-4.1.x86_64
libboost_atomic1_64_0-1.64.0-1.1.x86_64
libboost_atomic1_64_0-devel-1.64.0-1.1.x86_64
libboost_chrono1_64_0-1.64.0-1.1.x86_64
libboost_chrono1_64_0-devel-1.64.0-1.1.x86_64
libboost_container1_64_0-1.64.0-1.1.x86_64
libboost_container1_64_0-devel-1.64.0-1.1.x86_64
libboost_context1_64_0-1.64.0-1.1.x86_64
libboost_context1_64_0-devel-1.64.0-1.1.x86_64
libboost_coroutine1_64_0-1.64.0-1.1.x86_64
libboost_coroutine1_64_0-devel-1.64.0-1.1.x86_64
libboost_date_time1_64_0-1.64.0-1.1.x86_64
libboost_date_time1_64_0-devel-1.64.0-1.1.x86_64
libboost_fiber1_64_0-1.64.0-1.1.x86_64
libboost_fiber1_64_0-devel-1.64.0-1.1.x86_64
libboost_filesystem1_64_0-1.64.0-1.1.x86_64
libboost_filesystem1_64_0-devel-1.64.0-1.1.x86_64
libboost_graph1_64_0-1.64.0-1.1.x86_64
libboost_graph1_64_0-devel-1.64.0-1.1.x86_64
libboost_graph_parallel1_64_0-1.64.0-1.1.x86_64
libboost_graph_parallel1_64_0-devel-1.64.0-1.1.x86_64
libboost_headers1_64_0-devel-1.64.0-1.1.x86_64
libboost_iostreams1_64_0-1.64.0-1.1.x86_64
libboost_iostreams1_64_0-devel-1.64.0-1.1.x86_64
libboost_locale1_64_0-1.64.0-1.1.x86_64
libboost_locale1_64_0-devel-1.64.0-1.1.x86_64
libboost_log1_64_0-1.64.0-1.1.x86_64
libboost_log1_64_0-devel-1.64.0-1.1.x86_64
libboost_math1_64_0-1.64.0-1.1.x86_64
libboost_math1_64_0-devel-1.64.0-1.1.x86_64
libboost_mpi1_64_0-1.64.0-1.1.x86_64
libboost_mpi1_64_0-devel-1.64.0-1.1.x86_64
libboost_program_options1_64_0-1.64.0-1.1.x86_64
libboost_program_options1_64_0-devel-1.64.0-1.1.x86_64
libboost_python-py2_7-1_64_0-1.64.0-1.1.x86_64
libboost_python-py2_7-1_64_0-devel-1.64.0-1.1.x86_64
libboost_python-py3-1_64_0-1.64.0-1.1.x86_64
libboost_python-py3-1_64_0-devel-1.64.0-1.1.x86_64
libboost_random1_64_0-1.64.0-1.1.x86_64
libboost_random1_64_0-devel-1.64.0-1.1.x86_64
libboost_regex1_64_0-1.64.0-1.1.x86_64
libboost_regex1_64_0-devel-1.64.0-1.1.x86_64
libboost_serialization1_64_0-1.64.0-1.1.x86_64
libboost_serialization1_64_0-devel-1.64.0-1.1.x86_64
libboost_signals1_64_0-1.64.0-1.1.x86_64
libboost_signals1_64_0-devel-1.64.0-1.1.x86_64
libboost_system1_64_0-1.64.0-1.1.x86_64
libboost_system1_64_0-devel-1.64.0-1.1.x86_64
libboost_test1_64_0-1.64.0-1.1.x86_64
libboost_test1_64_0-devel-1.64.0-1.1.x86_64
libboost_thread1_64_0-1.64.0-1.1.x86_64
libboost_thread1_64_0-devel-1.64.0-1.1.x86_64
libboost_timer1_64_0-1.64.0-1.1.x86_64
libboost_timer1_64_0-devel-1.64.0-1.1.x86_64
libboost_type_erasure1_64_0-1.64.0-1.1.x86_64
libboost_type_erasure1_64_0-devel-1.64.0-1.1.x86_64
libboost_wave1_64_0-1.64.0-1.1.x86_64
libboost_wave1_64_0-devel-1.64.0-1.1.x86_64
libc++1-4.0.0-2.2.x86_64
libc++abi1-4.0.0-2.2.x86_64
libc++abi-devel-4.0.0-2.2.x86_64
libc++-devel-4.0.0-2.2.x86_64
libstdc++6-32bit-7.0.1+r246083-1.4.x86_64
libstdc++6-7.0.1+r246083-1.4.x86_64
libstdc++6-devel-gcc6-6.3.1+r245113-1.5.x86_64
libstdc++-devel-6-4.1.x86_64
$ uname -a
Linux socrates.i-pi.com 4.10.13-1-default #1 SMP PREEMPT Thu Apr 27 12:23:31
UTC 2017 (e5d11ce) x86_64 x86_64 x86_64 GNU/Linux

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >