Revert "boost: update to 1.69.0"
PATCH 1/1 Revert "boost: update to 1.69.0"
This reverts commit a384248938ea9db096866bf4ec8678d35ca62a12.
This package update slipped in doing the maint process. Removing it.
---
...bjam-native_1.69.0.bb => bjam-native_1.68.0.bb} | 0
.../boost/{boost-1.69.0.inc => boost-1.68.0.inc} | 4 +-
meta/recipes-support/boost/boost.inc | 1 +
...-arch-instruction-set-flags-we-do-that-o.patch} | 23 +-
...ucibility-add-file-directive-to-assembler.patch | 243 +++++++++++++++++++++
.../boost/{boost_1.69.0.bb => boost_1.68.0.bb} | 6 +-
6 files changed, 263 insertions(+), 14 deletions(-)
rename meta/recipes-support/boost/{bjam-native_1.69.0.bb => bjam-native_1.68.0.bb} (100%)
rename meta/recipes-support/boost/{boost-1.69.0.inc => boost-1.68.0.inc} (85%)
rename meta/recipes-support/boost/boost/{0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch => 0003-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch} (93%)
create mode 100644 meta/recipes-support/boost/boost/reproducibility-add-file-directive-to-assembler.patch
rename meta/recipes-support/boost/{boost_1.69.0.bb => boost_1.68.0.bb} (56%)meta/recipes-support/boost/bjam-native_1.68.0.bb renamed from meta/recipes-support/boost/bjam-native_1.69.0.bb +0 -0
meta/recipes-support/boost/boost-1.68.0.inc renamed from meta/recipes-support/boost/boost-1.69.0.inc +2 -2
@@ -12,8 +12,8 @@ BOOST_MAJ = "${@"_".join(d.getVar("PV").split(".")[0:2])}" BOOST_P = "boost_${BOOST_VER}" SRC_URI = "${SOURCEFORGE_MIRROR}/project/boost/boost/${PV}/${BOOST_P}.tar.bz2" -SRC_URI[md5sum] = "a1332494397bf48332cb152abfefcec2" -SRC_URI[sha256sum] = "8f32d4617390d1c2d16f26a27ab60d97807b35440d45891fa340fc2648b04406" +SRC_URI[md5sum] = "7fbd1890f571051f2a209681d57d486a" +SRC_URI[sha256sum] = "7f6130bc3cf65f56a618888ce9d5ea704fa10b462be126ad053e80e553d6d8b7" UPSTREAM_CHECK_URI = "http://www.boost.org/users/download/" UPSTREAM_CHECK_REGEX = "boostorg/release/(?P<pver>.*)/source/"
meta/recipes-support/boost/boost.inc +1 -0
@@ -21,6 +21,7 @@ BOOST_LIBS = "\ random \ regex \ serialization \ + signals \ system \ timer \ test \
meta/recipes-support/boost/boost/0003-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch renamed from meta/recipes-support/boost/boost/0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch +13 -10
@@ -1,20 +1,21 @@ -From 3e4eb02eb5951058bc6f8dffbf049eb189df8291 Mon Sep 17 00:00:00 2001 -From: Alexander Kanavin <[email protected]> -Date: Tue, 18 Dec 2018 15:42:57 +0100 -Subject: [PATCH] Don't set up arch/instruction-set flags, we do that ourselves +From 0868761e7d2d75d472090e3ef96f3d2f9ced27f3 Mon Sep 17 00:00:00 2001 +From: Christopher Larson <[email protected]> +Date: Tue, 13 Dec 2016 10:29:32 -0700 +Subject: [PATCH 5/6] Don't set up arch/instruction-set flags, we do that + ourselves Upstream-Status: Inappropriate Signed-off-by: Christopher Larson <[email protected]> -Signed-off-by: Alexander Kanavin <[email protected]> + --- - tools/build/src/tools/gcc.jam | 128 ---------------------------------- - 1 file changed, 128 deletions(-) + tools/build/src/tools/gcc.jam | 127 ------------------------------------------ + 1 file changed, 127 deletions(-) diff --git a/tools/build/src/tools/gcc.jam b/tools/build/src/tools/gcc.jam -index c57c773f..28618fb1 100644 +index e3b1b952..e4fc6c32 100644 --- a/tools/build/src/tools/gcc.jam +++ b/tools/build/src/tools/gcc.jam -@@ -1152,131 +1152,3 @@ local rule cpu-flags ( toolset variable : architecture : instruction-set + : +@@ -1276,130 +1276,3 @@ local rule cpu-flags ( toolset variable : architecture : instruction-set + : <architecture>$(architecture)/<instruction-set>$(instruction-set) : $(values) ; }
@@ -64,7 +65,6 @@ index c57c773f..28618fb1 100644 -cpu-flags gcc OPTIONS : x86 : skylake : -march=skylake ; -cpu-flags gcc OPTIONS : x86 : skylake-avx512 : -march=skylake-avx512 ; -cpu-flags gcc OPTIONS : x86 : cannonlake : -march=skylake-avx512 -mavx512vbmi -mavx512ifma -msha ; --cpu-flags gcc OPTIONS : x86 : icelake : -march=icelake ; -cpu-flags gcc OPTIONS : x86 : k6 : -march=k6 ; -cpu-flags gcc OPTIONS : x86 : k6-2 : -march=k6-2 ; -cpu-flags gcc OPTIONS : x86 : k6-3 : -march=k6-3 ;
@@ -146,3 +146,6 @@ index c57c773f..28618fb1 100644 -cpu-flags gcc OPTIONS : power : rs64a : -mcpu=rs64 ; -# AIX variant of RS/6000 & PowerPC -toolset.flags gcc AROPTIONS <address-model>64/<target-os>aix : "-X64" ; +-- +2.15.1 +
meta/recipes-support/boost/boost/reproducibility-add-file-directive-to-assembler.patch new file +243 -0
243 lines not on this page · raw message
meta/recipes-support/boost/boost_1.68.0.bb renamed from meta/recipes-support/boost/boost_1.69.0.bb +4 -2
@@ -1,9 +1,11 @@ require boost-${PV}.inc require boost.inc -SRC_URI += "file://arm-intrinsics.patch \ +SRC_URI += "\ + file://arm-intrinsics.patch \ file://boost-CVE-2012-2677.patch \ file://boost-math-disable-pch-for-gcc.patch \ file://0001-Apply-boost-1.62.0-no-forced-flags.patch.patch \ - file://0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch \ + file://0003-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch \ + file://reproducibility-add-file-directive-to-assembler.patch \ "
Signature · 1 line
2.7.4
Quoted 378 lines · Armin Kuster
This reverts commit
a384248938ea9db096866bf4ec8678d35ca62a12.This package update slipped in doing the maint process. Removing it.
Signed-off-by Armin Kuster <[email protected]>--- ...bjam-native_1.69.0.bb => bjam-native_1.68.0.bb} | 0 .../boost/{boost-1.69.0.inc => boost-1.68.0.inc} | 4 +- meta/recipes-support/boost/boost.inc | 1 + ...-arch-instruction-set-flags-we-do-that-o.patch} | 23 +- ...ucibility-add-file-directive-to-assembler.patch | 243 +++++++++++++++++++++ .../boost/{boost_1.69.0.bb => boost_1.68.0.bb} | 6 +- 6 files changed, 263 insertions(+), 14 deletions(-) rename meta/recipes-support/boost/{bjam-native_1.69.0.bb => bjam-native_1.68.0.bb} (100%) rename meta/recipes-support/boost/{boost-1.69.0.inc => boost-1.68.0.inc} (85%) rename meta/recipes-support/boost/boost/{0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch => 0003-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch} (93%) create mode 100644 meta/recipes-support/boost/boost/reproducibility-add-file-directive-to-assembler.patch rename meta/recipes-support/boost/{boost_1.69.0.bb => boost_1.68.0.bb} (56%)meta/recipes-support/boost/bjam-native_1.68.0.bb renamed from meta/recipes-support/boost/bjam-native_1.69.0.bb +0
-0meta/recipes-support/boost/boost-1.68.0.inc renamed from meta/recipes-support/boost/boost-1.69.0.inc +2
-2@@ -12,8 +12,8 @@ BOOST_MAJ = "${@"_".join(d.getVar("PV").split(".")[0:2])}" BOOST_P = "boost_${BOOST_VER}" SRC_URI = "${SOURCEFORGE_MIRROR}/project/boost/boost/${PV}/${BOOST_P}.tar.bz2" -SRC_URI[md5sum] = "a1332494397bf48332cb152abfefcec2" -SRC_URI[sha256sum] = "8f32d4617390d1c2d16f26a27ab60d97807b35440d45891fa340fc2648b04406" +SRC_URI[md5sum] = "7fbd1890f571051f2a209681d57d486a" +SRC_URI[sha256sum] = "7f6130bc3cf65f56a618888ce9d5ea704fa10b462be126ad053e80e553d6d8b7" UPSTREAM_CHECK_URI = "http://www.boost.org/users/download/" UPSTREAM_CHECK_REGEX = "boostorg/release/(?P<pver>.*)/source/"meta/recipes-support/boost/boost.inc +1
-0@@ -21,6 +21,7 @@ BOOST_LIBS = "\ random \ regex \ serialization \ + signals \ system \ timer \ test \meta/recipes-support/boost/boost/0003-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch renamed from meta/recipes-support/boost/boost/0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch +13
-10@@ -1,20 +1,21 @@ -From 3e4eb02eb5951058bc6f8dffbf049eb189df8291 Mon Sep 17 00:00:00 2001 -From: Alexander Kanavin <[email protected]> -Date: Tue, 18 Dec 2018 15:42:57 +0100 -Subject: [PATCH] Don't set up arch/instruction-set flags, we do that ourselves +From 0868761e7d2d75d472090e3ef96f3d2f9ced27f3 Mon Sep 17 00:00:00 2001 +From: Christopher Larson <[email protected]> +Date: Tue, 13 Dec 2016 10:29:32 -0700 +Subject: [PATCH 5/6] Don't set up arch/instruction-set flags, we do that + ourselves Upstream-Status: Inappropriate Signed-off-by: Christopher Larson <[email protected]> -Signed-off-by: Alexander Kanavin <[email protected]> + --- - tools/build/src/tools/gcc.jam | 128 ---------------------------------- - 1 file changed, 128 deletions(-) + tools/build/src/tools/gcc.jam | 127 ------------------------------------------ + 1 file changed, 127 deletions(-) diff --git a/tools/build/src/tools/gcc.jam b/tools/build/src/tools/gcc.jam -index c57c773f..28618fb1 100644 +index e3b1b952..e4fc6c32 100644 --- a/tools/build/src/tools/gcc.jam +++ b/tools/build/src/tools/gcc.jam -@@ -1152,131 +1152,3 @@ local rule cpu-flags ( toolset variable : architecture : instruction-set + : +@@ -1276,130 +1276,3 @@ local rule cpu-flags ( toolset variable : architecture : instruction-set + : <architecture>$(architecture)/<instruction-set>$(instruction-set) : $(values) ; }@@ -64,7 +65,6 @@ index c57c773f..28618fb1 100644 -cpu-flags gcc OPTIONS : x86 : skylake : -march=skylake ; -cpu-flags gcc OPTIONS : x86 : skylake-avx512 : -march=skylake-avx512 ; -cpu-flags gcc OPTIONS : x86 : cannonlake : -march=skylake-avx512 -mavx512vbmi -mavx512ifma -msha ; --cpu-flags gcc OPTIONS : x86 : icelake : -march=icelake ; -cpu-flags gcc OPTIONS : x86 : k6 : -march=k6 ; -cpu-flags gcc OPTIONS : x86 : k6-2 : -march=k6-2 ; -cpu-flags gcc OPTIONS : x86 : k6-3 : -march=k6-3 ;@@ -146,3 +146,6 @@ index c57c773f..28618fb1 100644 -cpu-flags gcc OPTIONS : power : rs64a : -mcpu=rs64 ; -# AIX variant of RS/6000 & PowerPC -toolset.flags gcc AROPTIONS <address-model>64/<target-os>aix : "-X64" ; +-- +2.15.1 +meta/recipes-support/boost/boost/reproducibility-add-file-directive-to-assembler.patch new file +243
-0@@ -0,0 +1,243 @@ +Author: Douglas Royds <[email protected]> +Date: Thu Nov 22 09:34:22 2018 +1300 + +Add a .file directive explicitly for all *_elf_gas.S files to prevent the linker +adding a host build-system path as a FILE symbol to the object file. + +This replaces the existing patch that added the .file directive to a small +subset of these files. + +Upstream-Status: Submitted [https://github.com/boostorg/context/issues/91] +Signed-off-by: Douglas Royds <[email protected]> + +diff -ur boost_1_68_0.original/libs/context/src/asm/jump_arm64_aapcs_elf_gas.S boost_1_68_0/libs/context/src/asm/jump_arm64_aapcs_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/jump_arm64_aapcs_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/jump_arm64_aapcs_elf_gas.S 2018-11-22 09:04:27.900876941 +1300 +@@ -51,6 +51,7 @@ + * * + *******************************************************/ + ++.file "jump_arm64_aapcs_elf_gas.S" + .text + .align 2 + .global jump_fcontext +diff -ur boost_1_68_0.original/libs/context/src/asm/jump_arm_aapcs_elf_gas.S boost_1_68_0/libs/context/src/asm/jump_arm_aapcs_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/jump_arm_aapcs_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/jump_arm_aapcs_elf_gas.S 2018-11-22 09:04:28.876898240 +1300 +@@ -38,6 +38,7 @@ + * * + *******************************************************/ + ++.file "jump_arm_aapcs_elf_gas.S" + .text + .globl jump_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/jump_i386_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/jump_i386_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/jump_i386_sysv_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/jump_i386_sysv_elf_gas.S 2018-11-22 09:04:29.904920674 +1300 +@@ -24,6 +24,7 @@ + * * + ****************************************************************************************/ + ++.file "jump_i386_sysv_elf_gas.S" + .text + .globl jump_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/jump_mips32_o32_elf_gas.S boost_1_68_0/libs/context/src/asm/jump_mips32_o32_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/jump_mips32_o32_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/jump_mips32_o32_elf_gas.S 2018-11-22 09:04:41.021163195 +1300 +@@ -38,6 +38,7 @@ + * * + * *****************************************************/ + ++.file "jump_mips32_o32_elf_gas.S" + .text + .globl jump_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/jump_ppc32_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/jump_ppc32_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/jump_ppc32_sysv_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/jump_ppc32_sysv_elf_gas.S 2018-11-22 09:04:42.281190679 +1300 +@@ -73,6 +73,7 @@ + * * + *******************************************************/ + ++.file "jump_ppc32_sysv_elf_gas.S" + .text + .globl jump_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/jump_ppc64_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/jump_ppc64_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/jump_ppc64_sysv_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/jump_ppc64_sysv_elf_gas.S 2018-11-22 09:04:43.193210571 +1300 +@@ -66,6 +66,7 @@ + * * + *******************************************************/ + ++.file "jump_ppc64_sysv_elf_gas.S" + .globl jump_fcontext + #if _CALL_ELF == 2 + .text +diff -ur boost_1_68_0.original/libs/context/src/asm/jump_x86_64_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/jump_x86_64_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/jump_x86_64_sysv_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/jump_x86_64_sysv_elf_gas.S 2018-11-22 09:04:44.213232818 +1300 +@@ -24,6 +24,7 @@ + * * + ****************************************************************************************/ + ++.file "jump_x86_64_sysv_elf_gas.S" + .text + .globl jump_fcontext + .type jump_fcontext,@function +diff -ur boost_1_68_0.original/libs/context/src/asm/make_arm64_aapcs_elf_gas.S boost_1_68_0/libs/context/src/asm/make_arm64_aapcs_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/make_arm64_aapcs_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/make_arm64_aapcs_elf_gas.S 2018-11-22 09:04:45.153253319 +1300 +@@ -51,6 +51,7 @@ + * * + *******************************************************/ + ++.file "make_arm64_aapcs_elf_gas.S" + .text + .align 2 + .global make_fcontext +diff -ur boost_1_68_0.original/libs/context/src/asm/make_arm_aapcs_elf_gas.S boost_1_68_0/libs/context/src/asm/make_arm_aapcs_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/make_arm_aapcs_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/make_arm_aapcs_elf_gas.S 2018-11-22 09:04:46.097273908 +1300 +@@ -38,6 +38,7 @@ + * * + *******************************************************/ + ++.file "make_arm_aapcs_elf_gas.S" + .text + .globl make_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/make_i386_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/make_i386_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/make_i386_sysv_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/make_i386_sysv_elf_gas.S 2018-11-22 09:04:46.973293012 +1300 +@@ -24,6 +24,7 @@ + * * + ****************************************************************************************/ + ++.file "make_i386_sysv_elf_gas.S" + .text + .globl make_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/make_mips32_o32_elf_gas.S boost_1_68_0/libs/context/src/asm/make_mips32_o32_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/make_mips32_o32_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/make_mips32_o32_elf_gas.S 2018-11-22 09:04:47.925313772 +1300 +@@ -38,6 +38,7 @@ + * * + * *****************************************************/ + ++.file "make_mips32_o32_elf_gas.S" + .text + .globl make_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/make_ppc32_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/make_ppc32_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/make_ppc32_sysv_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/make_ppc32_sysv_elf_gas.S 2018-11-22 09:04:48.865334271 +1300 +@@ -73,6 +73,7 @@ + * * + *******************************************************/ + ++.file "make_ppc32_sysv_elf_gas.S" + .text + .globl make_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/make_ppc64_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/make_ppc64_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/make_ppc64_sysv_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/make_ppc64_sysv_elf_gas.S 2018-11-22 09:04:50.049360089 +1300 +@@ -66,6 +66,7 @@ + * * + *******************************************************/ + ++.file "make_ppc64_sysv_elf_gas.S" + .globl make_fcontext + #if _CALL_ELF == 2 + .text +diff -ur boost_1_68_0.original/libs/context/src/asm/make_x86_64_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/make_x86_64_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/make_x86_64_sysv_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/make_x86_64_sysv_elf_gas.S 2018-11-22 09:04:51.117383378 +1300 +@@ -24,6 +24,7 @@ + * * + ****************************************************************************************/ + ++.file "make_x86_64_sysv_elf_gas.S" + .text + .globl make_fcontext + .type make_fcontext,@function +diff -ur boost_1_68_0.original/libs/context/src/asm/ontop_arm64_aapcs_elf_gas.S boost_1_68_0/libs/context/src/asm/ontop_arm64_aapcs_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/ontop_arm64_aapcs_elf_gas.S 2018-11-21 16:31:18.601760893 +1300 ++++ boost_1_68_0/libs/context/src/asm/ontop_arm64_aapcs_elf_gas.S 2018-11-22 09:04:52.201407013 +1300 +@@ -51,6 +51,7 @@ + * * + *******************************************************/ + ++.file "ontop_arm64_aapcs_elf_gas.S" + .text + .align 2 + .global ontop_fcontext +diff -ur boost_1_68_0.original/libs/context/src/asm/ontop_arm_aapcs_elf_gas.S boost_1_68_0/libs/context/src/asm/ontop_arm_aapcs_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/ontop_arm_aapcs_elf_gas.S 2018-11-21 16:31:18.605760935 +1300 ++++ boost_1_68_0/libs/context/src/asm/ontop_arm_aapcs_elf_gas.S 2018-11-22 09:04:53.269430300 +1300 +@@ -38,6 +38,7 @@ + * * + *******************************************************/ + ++.file "ontop_arm_aapcs_elf_gas.S" + .text + .globl ontop_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/ontop_i386_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/ontop_i386_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/ontop_i386_sysv_elf_gas.S 2018-11-21 16:31:18.605760935 +1300 ++++ boost_1_68_0/libs/context/src/asm/ontop_i386_sysv_elf_gas.S 2018-11-22 09:04:54.389454719 +1300 +@@ -24,6 +24,7 @@ + * * + ****************************************************************************************/ + ++.file "ontop_i386_sysv_elf_gas.S" + .text + .globl ontop_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/ontop_mips32_o32_elf_gas.S boost_1_68_0/libs/context/src/asm/ontop_mips32_o32_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/ontop_mips32_o32_elf_gas.S 2018-11-21 16:31:18.605760935 +1300 ++++ boost_1_68_0/libs/context/src/asm/ontop_mips32_o32_elf_gas.S 2018-11-22 09:04:55.657482363 +1300 +@@ -38,6 +38,7 @@ + * * + * *****************************************************/ + ++.file "ontop_mips32_o32_elf_gas.S" + .text + .globl ontop_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/ontop_ppc32_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/ontop_ppc32_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/ontop_ppc32_sysv_elf_gas.S 2018-11-21 16:31:18.605760935 +1300 ++++ boost_1_68_0/libs/context/src/asm/ontop_ppc32_sysv_elf_gas.S 2018-11-22 09:04:56.777506781 +1300 +@@ -73,6 +73,7 @@ + * * + *******************************************************/ + ++.file "ontop_ppc32_sysv_elf_gas.S" + .text + .globl ontop_fcontext + .align 2 +diff -ur boost_1_68_0.original/libs/context/src/asm/ontop_ppc64_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/ontop_ppc64_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/ontop_ppc64_sysv_elf_gas.S 2018-11-21 16:31:18.605760935 +1300 ++++ boost_1_68_0/libs/context/src/asm/ontop_ppc64_sysv_elf_gas.S 2018-11-22 09:04:58.485544015 +1300 +@@ -66,6 +66,7 @@ + * * + *******************************************************/ + ++.file "ontop_ppc64_sysv_elf_gas.S" + .globl ontop_fcontext + #if _CALL_ELF == 2 + .text +diff -ur boost_1_68_0.original/libs/context/src/asm/ontop_x86_64_sysv_elf_gas.S boost_1_68_0/libs/context/src/asm/ontop_x86_64_sysv_elf_gas.S +--- boost_1_68_0.original/libs/context/src/asm/ontop_x86_64_sysv_elf_gas.S 2018-11-21 16:31:18.605760935 +1300 ++++ boost_1_68_0/libs/context/src/asm/ontop_x86_64_sysv_elf_gas.S 2018-11-22 09:04:59.609568516 +1300 +@@ -24,6 +24,7 @@ + * * + ****************************************************************************************/ + ++.file "ontop_x86_64_sysv_elf_gas.S" + .text + .globl ontop_fcontext + .type ontop_fcontext,@functionmeta/recipes-support/boost/boost_1.68.0.bb renamed from meta/recipes-support/boost/boost_1.69.0.bb +4
-3@@ -1,9 +1,11 @@ require boost-${PV}.inc require boost.inc -SRC_URI += "file://arm-intrinsics.patch \ +SRC_URI += "\ + file://arm-intrinsics.patch \ file://boost-CVE-2012-2677.patch \ file://boost-math-disable-pch-for-gcc.patch \ file://0001-Apply-boost-1.62.0-no-forced-flags.patch.patch \ - file://0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch \ + file://0003-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch \ + file://reproducibility-add-file-directive-to-assembler.patch \ " --
Quoted 2 lines
2.7.4
Just my opinion - don't consider this as NAK.
* I already fixed the recipes that failed for me. For at least one the change is no more compatible to 1.68.0.
* This makes PV going backwards
Thanks for addressing - what do others think?
Andreas
Quoted 5 lines · Andreas Müller
Quoted 4 lines · Armin Kuster
This reverts commit
a384248938ea9db096866bf4ec8678d35ca62a12.This package update slipped in doing the maint process. Removing it.
<snip>
Quoted 7 lines
Just my opinion - don't consider this as NAK.
* I already fixed the recipes that failed for me. For at least one the change is no more compatible to 1.68.0.
* This makes PV going backwardsThanks for addressing - what do others think?
I'm not using thud yet, but updating boost in stable branch would break too many things and I would have to revert that change in our trees. Some boost updates are in the end quite trivial and just require recompiling everything but still, I would prefer that boost is not updated in stable branches unless there is a huge security/stability issue with the old version.
Hope this helps,
-Mikko
Quoted 13 lines · On Tue, Mar 19, 2019 at 07:52:06AM +0000, [email protected] wrote:
Quoted 5 lines · Andreas Müller
Quoted 4 lines · Armin Kuster
This reverts commit
a384248938ea9db096866bf4ec8678d35ca62a12.This package update slipped in doing the maint process. Removing it.
<snip>
Quoted 6 lines
Just my opinion - don't consider this as NAK.
* I already fixed the recipes that failed for me. For at least one the change is no more compatible to 1.68.0.
* This makes PV going backwards
Quoted 7 lines
Quoted 1 line
Thanks for addressing - what do others think?
I'm not using thud yet, but updating boost in stable branch would break too many things and I would have to revert that change in our trees. Some boost updates are in the end quite trivial and just require recompiling everything but still, I would prefer that boost is not updated in stable branches unless there is a huge
security/stabilityissue with the old version.
Agreed.
I care less for PV going backwards nowadays, it's probably less annoying than bumping PE first in master and then backporting PE bump to thud.
People with build issues related to boost upgrade probably never built whole image to push it as an upgrade to end devices.
Cheers,
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 19 lines · Martin Jansa
Quoted 12 lines · On Tue, Mar 19, 2019 at 07:52:06AM +0000, [email protected] wrote:
Quoted 4 lines · Andreas Müller
Quoted 3 lines · Armin Kuster
This reverts commit
a384248938ea9db096866bf4ec8678d35ca62a12.This package update slipped in doing the maint process. Removing it.
<snip>
Quoted 6 lines
Just my opinion - don't consider this as NAK.
* I already fixed the recipes that failed for me. For at least one the change is no more compatible to 1.68.0.
* This makes PV going backwardsQuoted 6 lines
Quoted 1 line
Thanks for addressing - what do others think?
I'm not using thud yet, but updating boost in stable branch would break too many things and I would have to revert that change in our trees. Some boost updates are in the end quite trivial and just require recompiling everything but still, I would prefer that boost is not updated in stable branches unless there is a huge
security/stabilityissue with the old version.
Quoted 7 lines
Agreed.
I care less for PV going backwards nowadays, it's probably less annoying than bumping PE first in master and then backporting PE bump to thud.
People with build issues related to boost upgrade probably never built whole image to push it as an upgrade to end devices.
So do you agree with the revert?
-a rmin
Quoted 3 lines
Cheers,
Quoted 24 lines · On Sun, Mar 24, 2019 at 11:45:08AM -0700, akuster808 wrote:
Quoted 21 lines · Martin Jansa
Quoted 12 lines · On Tue, Mar 19, 2019 at 07:52:06AM +0000, [email protected] wrote:
Quoted 4 lines · Andreas Müller
Quoted 3 lines · Armin Kuster
This reverts commit
a384248938ea9db096866bf4ec8678d35ca62a12.This package update slipped in doing the maint process. Removing it.
<snip>
Quoted 6 lines
Just my opinion - don't consider this as NAK.
* I already fixed the recipes that failed for me. For at least one the change is no more compatible to 1.68.0.
* This makes PV going backwardsQuoted 6 lines
Quoted 1 line
Thanks for addressing - what do others think?
I'm not using thud yet, but updating boost in stable branch would break too many things and I would have to revert that change in our trees. Some boost updates are in the end quite trivial and just require recompiling everything but still, I would prefer that boost is not updated in stable branches unless there is a huge
security/stabilityissue with the old version.Agreed.
Quoted 7 lines
Quoted 5 lines
I care less for PV going backwards nowadays, it's probably less annoying than bumping PE first in master and then backporting PE bump to thud.
People with build issues related to boost upgrade probably never built whole image to push it as an upgrade to end devices.
So do you agree with the revert?
I do.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Any update on this one? Or should we downgrade it on our side when bumping oe-core/thud revision?
Quoted 45 lines · Martin Jansa
Quoted 6 lines · On Sun, Mar 24, 2019 at 11:45:08AM -0700, akuster808 wrote:
Quoted 3 lines · Martin Jansa
Quoted 2 lines · On Tue, Mar 19, 2019 at 07:52:06AM +0000, [email protected] wrote:
Quoted 1 line · Andreas Müller
On Mon, Mar 18, 2019 at 5:45 PM Armin Kuster <[email protected]>
Quoted 7 lines · wrote:
Quoted 7 lines
Quoted 7 lines
Quoted 3 lines
Quoted 3 lines
This reverts commit
a384248938ea9db096866bf4ec8678d35ca62a12.This package update slipped in doing the maint process. Removing it.
<snip>
Quoted 3 lines
Just my opinion - don't consider this as NAK.
* I already fixed the recipes that failed for me. For at least one
the
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
change is no more compatible to 1.68.0.
* This makes PV going backwardsThanks for addressing - what do others think?
I'm not using thud yet, but updating boost in stable branch would
break
Quoted 1 line
Quoted 1 line
Quoted 1 line
too many things and I would have to revert that change in our trees.
Some boost
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
updates are in the end quite trivial and just require recompiling everything but still, I would prefer that boost is not updated in
stable
Quoted 1 line
Quoted 1 line
Quoted 1 line
branches unless there is a huge
security/stabilityissue with the oldversion.
Quoted 3 lines
Quoted 3 lines
Agreed.
I care less for PV going backwards nowadays, it's probably less
annoying than
Quoted 6 lines
Quoted 4 lines
bumping PE first in master and then backporting PE bump to thud.
People with build issues related to boost upgrade probably never built whole image to push it as an upgrade to end devices.
So do you agree with the revert?
I do.
--
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 2 lines · Martin Jansa
Any update on this one? Or should we downgrade it on our side when bumping oe-core/thud revision?
I have this stagged but it missed the QA cutoff.
- armin
Quoted 52 lines
On Sun, Mar 24, 2019 at 7:48 PM Martin Jansa <[email protected] <mailto:[email protected]>> wrote:
On Sun, Mar 24, 2019 at 11:45:08AM -0700, akuster808 wrote:
>
>
> On 3/24/19 11:01 AM, Martin Jansa wrote:
> > On Tue, Mar 19, 2019 at 07:52:06AM +0000, [email protected] <mailto:[email protected]> wrote:
> >> On Mon, Mar 18, 2019 at 06:03:05PM +0100, Andreas Müller wrote:
> >>> On Mon, Mar 18, 2019 at 5:45 PM Armin Kuster <[email protected] <mailto:[email protected]>> wrote:
> >>>> This reverts commita384248938ea9db096866bf4ec8678d35ca62a12. > >>>>
> >>>> This package update slipped in doing the maint process. Removing it.
> >> <snip>
> >>> Just my opinion - don't consider this as NAK.
> >>>
> >>> * I already fixed the recipes that failed for me. For at least one the
> >>> change is no more compatible to 1.68.0.
> >>> * This makes PV going backwards
> >>>
> >>> Thanks for addressing - what do others think?
> >> I'm not using thud yet, but updating boost in stable branch would break
> >> too many things and I would have to revert that change in our trees. Some boost
> >> updates are in the end quite trivial and just require recompiling > >> everything but still, I would prefer that boost is not updated in stable
> >> branches unless there is a hugesecurity/stabilityissue with the old version.
> > Agreed.
> >
> > I care less for PV going backwards nowadays, it's probably less annoying than
> > bumping PE first in master and then backporting PE bump to thud. > >
> > People with build issues related to boost upgrade probably never > > built whole image to push it as an upgrade to end devices. >
> So do you agree with the revert?I do.
--
Martin 'JaMa' Jansa jabber: [email protected] <mailto:[email protected]>