From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Cc: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
Subject: [PATCH 0/2] boost: upgrade 1.91.0 -> 1.92.0
Date: Sun, 16 Aug 2026 18:26:09 +0200 [thread overview]
Message-ID: <20260816162611.41933-1-jaipaul.cheernam@est.tech> (raw)
Upgrade boost and boost-build-native to 1.92.0.
Includes a backport for boost.histogram build failure and a fix
for boost.predef installing unneeded b2 tooling.
Jaipaul Cheernam (2):
boost-build-native: upgrade 1.91.0 -> 1.92.0
boost: upgrade 1.91.0 -> 1.92.0
.../{boost-1.91.0.inc => boost-1.92.0.inc} | 2 +-
...1.91.0.bb => boost-build-native_1.92.0.bb} | 2 +-
meta/recipes-support/boost/boost.inc | 4 +
...h-instruction-set-flags-we-do-that-o.patch | 4 +-
...01-dont-setup-compiler-flags-m32-m64.patch | 4 +-
...b2-project-requirements-out-of-build.patch | 85 +++++++++++++++++++
.../boost-math-disable-pch-for-gcc.patch | 2 +-
.../{boost_1.91.0.bb => boost_1.92.0.bb} | 1 +
8 files changed, 97 insertions(+), 7 deletions(-)
rename meta/recipes-support/boost/{boost-1.91.0.inc => boost-1.92.0.inc} (90%)
rename meta/recipes-support/boost/{boost-build-native_1.91.0.bb => boost-build-native_1.92.0.bb} (92%)
create mode 100644 meta/recipes-support/boost/boost/0001-histogram-move-b2-project-requirements-out-of-build.patch
rename meta/recipes-support/boost/{boost_1.91.0.bb => boost_1.92.0.bb} (76%)
next reply other threads:[~2026-08-16 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 16:26 Jaipaul Cheernam [this message]
2026-08-16 16:26 ` [PATCH 1/2] boost-build-native: upgrade 1.91.0 -> 1.92.0 Jaipaul Cheernam
2026-08-16 16:26 ` [PATCH 2/2] boost: " Jaipaul Cheernam
2026-08-17 11:09 ` [OE-core] " Alexander Kanavin
2026-08-17 11:22 ` Jaipaul Cheernam
2026-08-17 13:02 ` [PATCH v2 0/2] " Jaipaul Cheernam
2026-08-17 13:02 ` [PATCH v2 1/2] boost-build-native: " Jaipaul Cheernam
2026-08-17 13:03 ` [PATCH v2 2/2] boost: " Jaipaul Cheernam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260816162611.41933-1-jaipaul.cheernam@est.tech \
--to=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.