Package: boost1.55 / 1.55.0+dfsg-3

Metadata

Package Version Patches format
boost1.55 1.55.0+dfsg-3 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
chrono duration.patch | (download)

boost/chrono/duration.hpp | 24 12 + 12 - 0 !
1 file changed, 12 insertions(+), 12 deletions(-)

 fix conflict between chrono/duration.hpp and apache2/httpd.h
 The former defines a type named "CR" while the latter #defines CR.
pythonid.patch | (download)

boostcpp.jam | 8 0 + 8 - 0 !
libs/mpi/build/Jamfile.v2 | 9 9 + 0 - 0 !
libs/python/build/Jamfile.v2 | 10 10 + 0 - 0 !
3 files changed, 19 insertions(+), 8 deletions(-)

 fix jam option --python-buildid
mpi allocator c++0x.patch | (download)

boost/mpi/allocator.hpp | 6 6 + 0 - 0 !
1 file changed, 6 insertions(+)

 fix include of <boost/mpi.hpp> on gcc < 4.6.3
 Workaround proposed in boost Trac ticket to allow using
 -std=c++0x with gcc 4.6.  It turns out to be a gcc
 bug that is fixed for gcc 4.6.3 and 4.7.
fix ftbfs python 3.3.patch | (download)

tools/build/v2/tools/python.jam | 4 3 + 1 - 0 !
1 file changed, 3 insertions(+), 1 deletion(-)

 python3.3 has an extra multiarch include location
hurd clock gettime.patch | (download)

libs/log/src/timestamp.cpp | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 boost1.54 currently ftbfs on hurd-i386 because it doesn't know hurd-i386
 has clock_gettime. hurd-i386 does not define _POSIX_TIMERS because it
 does not have timer_create & co yet, but it does have clock_gettime,
 thus the attached patch.
Bug: 714847



hppa long double config.patch | (download)

boost/math/tools/config.hpp | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 fix definition of boost_math_no_long_double_math_functions for hppa
boost 1.55.0 001 log_fix_dump_avx2.patch | (download)

libs/log/src/dump_avx2.cpp | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fixes incorrect output of the dump manipulator, when used on avx2-enabled cpu (e.g. intel haswell)
ELFv2 libboost1.54 dev context asm.patch | (download)

libs/context/src/asm/jump_ppc64_sysv_elf_gas.S | 50 38 + 12 - 0 !
libs/context/src/asm/make_ppc64_sysv_elf_gas.S | 45 35 + 10 - 0 !
2 files changed, 73 insertions(+), 22 deletions(-)

---
boost python examples.patch | (download)

libs/python/example/Jamroot | 20 8 + 12 - 0 !
libs/python/example/tutorial/Jamroot | 14 2 + 12 - 0 !
2 files changed, 10 insertions(+), 24 deletions(-)

 patch to build examples using installed boost.python
boost 1.55 128bit_int_support.patch | (download)

boost/atomic/detail/cas128strong.hpp | 10 7 + 3 - 0 !
boost/atomic/detail/gcc-atomic.hpp | 17 12 + 5 - 0 !
2 files changed, 19 insertions(+), 8 deletions(-)

 handle 128-bit values when native support for 128-bit integers not available
ppc64el fp_traits ibm long double.patch | (download)

boost/math/special_functions/detail/fp_traits.hpp | 9 8 + 1 - 0 !
1 file changed, 8 insertions(+), 1 deletion(-)

 [patch] math: fix fp_traits for ibm long double

This patch fixes the fp_traits_non_native template specialization for
IBM long double.  Current interface does not work correctly for the type
due to the fact that for some operations (sign manipulation, for instance), both
double should be manipulated.  For other operations that only require
the 32 most significand bits (isinf/isnan for instance), the double
specialization is suffient.

This fixes the issues for geometry test in PPC64LE environment with no
regressions on PPC64BE.