|
From: | GNU bug Tracking System |
Subject: | bug#46562: closed ([PATCH] gnu: gperftools: Update to 2.8.1.) |
Date: | Thu, 18 Feb 2021 18:05:01 +0000 |
Your message dated Thu, 18 Feb 2021 13:04:32 -0500 with message-id <YC6sMJrAkep1woy2@jasmine.lan> and subject line Re: [bug#46562] [PATCH] gnu: gperftools: Update to 2.8.1. has caused the debbugs.gnu.org bug report #46562, regarding [PATCH] gnu: gperftools: Update to 2.8.1. to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 46562: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=46562 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: [PATCH] gnu: gperftools: Update to 2.8.1. Date: Tue, 16 Feb 2021 08:47:23 -0500 From cc9e4c7fdfb872685181715def0d14d35069f76d Mon Sep 17 00:00:00 2001From: Greg Hogan <code@greghogan.com>Date: Thu, 11 Feb 2021 19:08:35 +0000Subject: [PATCH] gnu: gperftools: Update to 2.8.1.* gnu/packages/cpp.scm (gperftools): Update to 2.8.1.---gnu/packages/cpp.scm | 4 ++--1 file changed, 2 insertions(+), 2 deletions(-)diff --git a/gnu/packages/cpp.scm b/gnu/packages/cpp.scmindex ae47490755..10d756a564 100644--- a/gnu/packages/cpp.scm+++ b/gnu/packages/cpp.scm@@ -512,7 +512,7 @@ maintained anymore.")(define-public gperftools(package(name "gperftools")- (version "2.8")+ (version "2.8.1")(source(origin(method git-fetch)@@ -520,7 +520,7 @@ maintained anymore.")(commit (string-append "gperftools-" version))))(sha256- (base32 "1rnc53kaxlljgbpsff906vdsry9jl9gcvcnmxgkprwzxq1wipyd0"))+ (base32 "19bj2vlsbfwq7m826v2ccqg47kd7cb5vcz1yw2x0v5qzhaxbakk1"))(file-name (git-file-name name version))))(build-system gnu-build-system)(native-inputs--2.30.00001-gnu-gperftools-Update-to-2.8.1.patch
Description: Binary data
--- End Message ---
--- Begin Message ---Subject: Re: [bug#46562] [PATCH] gnu: gperftools: Update to 2.8.1. Date: Thu, 18 Feb 2021 13:04:32 -0500 On Thu, Feb 18, 2021 at 09:58:39AM +0200, Efraim Flashner wrote: > Did you try sending it through again? It built without any problems on > my machine (with more cores) Yeah, it fails consistently on my i5-6300U [0], using a tmpfs for the build directory on Linux 5.11. It works when I set #:parallel-tests? #f, so I've pushed Greg's patch with that modification as 7cd0247eb4d22d47f76e26fd7b65ec45cb5d7ccb [0] 2 cores, "4 threads"signature.asc
Description: PGP signature
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |