From: Greg Hogan <code@greghogan.com>
To: 57492@debbugs.gnu.org
Cc: Greg Hogan <code@greghogan.com>
Subject: [bug#57492] [PATCH core-updates] gnu: boost: Update to 1.80.0.
Date: Tue, 30 Aug 2022 16:36:24 +0000 [thread overview]
Message-ID: <6e6c289860d63d17dbcf7295c912e20fe2df164b.1661877251.git.code@greghogan.com> (raw)
* gnu/packages/boost.scm (boost): Update to 1.80.0.
[source](patches): Add new and remove old upstream patches.
---
gnu/packages/boost.scm | 26 ++++++++++++++++++++------
1 file changed, 20 insertions(+), 6 deletions(-)
diff --git a/gnu/packages/boost.scm b/gnu/packages/boost.scm
index 818669b757..55296889b8 100644
--- a/gnu/packages/boost.scm
+++ b/gnu/packages/boost.scm
@@ -68,7 +68,7 @@ (define (boost-patch name version hash)
(define-public boost
(package
(name "boost")
- (version "1.79.0")
+ (version "1.80.0")
(source (origin
(method url-fetch)
(uri (string-append "https://boostorg.jfrog.io/artifactory/main/release/"
@@ -76,13 +76,27 @@ (define-public boost
(version-with-underscores version) ".tar.bz2"))
(patches
(list (boost-patch
- ;; 1.79.0 was released with a segmentation fault:
- ;; <https://github.com/boostorg/json/issues/692>.
- "0001-json-array-erase-relocate.patch" version
- "1b0izwj8w92imr8ydzrh522syncprpf82n3kcy6apxn6p54b7p0f")))
+ ;; Boost.Filesystem directory iterators may fail to
+ ;; construct for a network share on Windows prior to 10:
+ ;; https://github.com/boostorg/filesystem/pull/246,
+ ;; https://github.com/boostorg/filesystem/issues/245
+ "0001-filesystem-win-fix-dir-it-net-share.patch" version
+ "067hhylqkzzdbqzc1hkbpaqmvz248lxqrdhb2yi6iq9qabsik3lk")
+ (boost-patch
+ ;; In Boost.Filesystem on Windows, weakly_canonical fails
+ ;; to process paths that start with the "\\?\" prefix:
+ ;; https://github.com/boostorg/filesystem/issues/247
+ "0002-filesystem-fix-weakly-canonical-long-paths.patch" version
+ "00w3albf8527glclx85p5b2ml3vr06xpwwmfyzg005v1cp8avcpi")
+ (boost-patch
+ ;; Boost.Unordered containers are not in a valid state
+ ;; after moving:
+ ;; https://github.com/boostorg/unordered/issues/139
+ "0003-unordered-valid-after-move.patch" version
+ "0dw839w22cawqawfpsx7j7v9y0x2vn66m732iidpxvdxbjn2kzva")))
(sha256
(base32
- "0fggarccddj6q4ifj3kn7g565rbhn4ia1vd45fxb7y57a6fmhpa7"))))
+ "1h00qp4z5k6lfz310xjwsmqs8fwxi6ngas51169cafz4h9fmc68y"))))
(build-system gnu-build-system)
(inputs
(append
--
2.37.2
next reply other threads:[~2022-08-30 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 16:36 Greg Hogan [this message]
2022-08-30 19:50 ` [bug#57492] [PATCH core-updates] gnu: boost: Update to 1.80.0 Maxime Devos
2022-08-30 20:15 ` Greg Hogan
2022-08-31 13:43 ` [bug#57492] [PATCH core-updates v2] " Greg Hogan
2022-09-01 21:00 ` bug#57492: " Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6e6c289860d63d17dbcf7295c912e20fe2df164b.1661877251.git.code@greghogan.com \
--to=code@greghogan.com \
--cc=57492@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).