Ok. I've seen that in the qpid bugtracker already and I've patched it.
While re-building, I've noticed that libboost-all-dev installs 1.46
boost packages. Did you use libboost1.48-all-dev or is there something
wrong on my side?
$ apt-cache show libboost-all-dev
Package: libboost-all-dev
Source: boost-defaults
Version: 1.48.0.2
Installed-Size: 26
Maintainer: Debian Boost Team <pkg-boost-de...@lists.alioth.debian.org>
Architecture: amd64
Depends: libboost-dev, libboost-date-time-dev, libboost-filesystem-dev,
libboost-graph-dev, libboost-graph-parallel-dev, libboost-iostreams-dev,
libboost-math-dev, libboost-mpi-dev, libboost-mpi-python-dev,
libboost-program-options-dev, libboost-python-dev, libboost-regex-dev,
libboost-serialization-dev, libboost-signals-dev, libboost-system-dev,
libboost-test-dev, libboost-thread-dev, libboost-wave-dev
Description: Boost C++ Libraries development files (ALL, default
version)
The Boost web site provides free, peer-reviewed, portable C++ source
libraries. The emphasis is on libraries which work well with the C++
Standard Library. One goal is to establish "existing practice" and
provide reference implementations so that the Boost libraries are
suitable for eventual standardization. Some of the libraries have
already been proposed for inclusion in the C++ Standards Committee's
upcoming C++ Standard Library Technical Report.
.
This package provides the complete Boost development environment,
including all separately-packaged libraries.
.
This package is a dependency package, which depends on Debian's
default
Boost version (currently 1.46).
Homepage: http://www.boost.org/
Tag: devel::library
Section: libdevel
Priority: optional
Filename:
pool/main/b/boost-defaults/libboost-all-dev_1.48.0.2_amd64.deb
Size: 2928
MD5sum: abfef854f6f4669bc367b8b0b43fb448
SHA1: 28b62a6284ba585538b0d93e073ac045a9be8ed8
SHA256:
b2955ffa2b560e8d9dc55cf8a9e7ffad2b0a0f997e2dd1ef444e67bedfa78f9b
and
$ sudo apt-get install libboost-all-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
gccxml libboost-date-time-dev libboost-date-time1.46-dev
libboost-date-time1.46.1 libboost-dev libboost-filesystem-dev
libboost-filesystem1.46-dev libboost-graph-dev
libboost-graph-parallel-dev libboost-graph-parallel1.46-dev
libboost-graph-parallel1.46.1 libboost-graph1.46-dev
libboost-graph1.46.1 libboost-iostreams-dev libboost-iostreams1.46-dev
libboost-math-dev libboost-math1.46-dev libboost-math1.46.1
libboost-mpi-dev libboost-mpi-python-dev libboost-mpi1.46-dev
libboost-mpi1.46.1 libboost-program-options-dev
libboost-program-options1.46-dev libboost-python-dev
libboost-python1.46-dev
libboost-regex-dev libboost-regex1.46-dev libboost-serialization-dev
libboost-serialization1.46-dev libboost-serialization1.46.1
libboost-signals-dev libboost-signals1.46-dev libboost-system-dev
libboost-system1.46-dev libboost-test-dev libboost-test1.46-dev
libboost-test1.46.1 libboost-thread-dev libboost-thread1.46-dev
libboost-wave-dev libboost-wave1.46-dev libboost-wave1.46.1
libboost1.46-dev libibverbs-dev libibverbs1 libicu-dev libnuma1
libopenmpi-dev libopenmpi1.3 libtorque2 mpi-default-dev
openmpi-common
Suggested packages:
libboost1.46-doc libboost-random1.46-dev xsltproc doxygen default-jdk
fop icu-doc
Am 31.12.2011 01:56, schrieb Steve M. Robbins:
Source: qpid-cpp
Version: 0.12-3
Severity: normal
Package failed to build with new Boost 1.48:
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include
-I. -I=. -D_FORTIFY_SOURCE=2 -Werror -pedantic -Wall -Wextra
-Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long
-Wvolatile-register-var -Winvalid-pch -Wno-system-headers
-Woverloaded-vi
rtual -DQPID_LIBEXEC_DIR=\"/usr/lib/qpid\"
-DBOOST_FILESYSTEM_VERSION=2 -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Wformat-security
-Werror=format-security -c qpid/framing/Uuid.cpp -fPIC -DPIC -o
qpid/framing/.libs/Uuid.o
/bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H
-I. -I../include -I../include -I. -I=. -D_FORTIFY_SOURCE=2 -Werror
-pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual
-Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch
-Wno-
system-headers -Woverloaded-virtual
-DQPID_LIBEXEC_DIR=\"/usr/lib/qpid\" -DBOOST_FILESYSTEM_VERSION=2 -g
-O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -Werror=format-security -c -o qpid/log/Logger.lo
qpid/log/Logger.cpp
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include
-I. -I=. -D_FORTIFY_SOURCE=2 -Werror -pedantic -Wall -Wextra
-Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long
-Wvolatile-register-var -Winvalid-pch -Wno-system-headers
-Woverloaded-vi
rtual -DQPID_LIBEXEC_DIR=\"/usr/lib/qpid\"
-DBOOST_FILESYSTEM_VERSION=2 -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Wformat-security
-Werror=format-security -c qpid/log/Logger.cpp -fPIC -DPIC -o
qpid/log/.libs/Logger.o
qpid/log/Logger.cpp:26:43: fatal error:
boost/pool/detail/singleton.hpp: No such file or directory
compilation terminated.
make[4]: *** [qpid/log/Logger.lo] Error 1
Prior to 1.48, Boost.Pool used a singleton base class. It was an
implementation detail, now removed, but some external packages
depended upon it. This is an upstream bug, since the class was never
intended as a public interface.
The breakage may manifest in a couple of ways:
* boost/pool/detail/singleton.hpp: No such file or directory
* 'singleton_default' in namespace 'boost::details::pool' does not
name a type
The class in singleton.hpp is small enough that it could simply be
included directly into the using source code.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
