From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id OIkcBDocVF+eWgAA0tVLHw (envelope-from ) for ; Sat, 05 Sep 2020 23:16:10 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id SBEQADocVF/CIQAAbx9fmQ (envelope-from ) for ; Sat, 05 Sep 2020 23:16:10 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 803E19404C2 for ; Sat, 5 Sep 2020 23:16:09 +0000 (UTC) Received: from localhost ([::1]:53280 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kEhPk-0006Z9-68 for larch@yhetil.org; Sat, 05 Sep 2020 19:16:08 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:47734) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kEhPe-0006Z3-8N for bug-guix@gnu.org; Sat, 05 Sep 2020 19:16:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:32808) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kEhPd-0002b3-V5 for bug-guix@gnu.org; Sat, 05 Sep 2020 19:16:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kEhPd-00039n-QI for bug-guix@gnu.org; Sat, 05 Sep 2020 19:16:01 -0400 X-Loop: help-debbugs@gnu.org Subject: bug#43228: r-v8 doesn't build since node 10.22 update Resent-From: Mark H Weaver Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Sat, 05 Sep 2020 23:16:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43228 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: Pierre Langlois Received: via spool by 43228-submit@debbugs.gnu.org id=B43228.159934770812070 (code B ref 43228); Sat, 05 Sep 2020 23:16:01 +0000 Received: (at 43228) by debbugs.gnu.org; 5 Sep 2020 23:15:08 +0000 Received: from localhost ([127.0.0.1]:44354 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kEhOl-00038c-UR for submit@debbugs.gnu.org; Sat, 05 Sep 2020 19:15:08 -0400 Received: from world.peace.net ([64.112.178.59]:60722) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kEhOk-00037n-1N for 43228@debbugs.gnu.org; Sat, 05 Sep 2020 19:15:06 -0400 Received: from mhw by world.peace.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kEhOe-0006yk-Eh; Sat, 05 Sep 2020 19:15:00 -0400 From: Mark H Weaver In-Reply-To: <87blikhvj2.fsf@gmx.com> References: <87sgbwi0dn.fsf@gmx.com> <87tuwcqdek.fsf@netris.org> <87blikhvj2.fsf@gmx.com> Date: Sat, 05 Sep 2020 19:13:46 -0400 Message-ID: <87o8mjrf3u.fsf@netris.org> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-Spam-Score: -1.0 (-) X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: 43228@debbugs.gnu.org Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: "bug-Guix" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of bug-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=bug-guix-bounces@gnu.org X-Spam-Score: -1.01 X-TUID: Ek2vHutaJ90F Hi Pierre, Pierre Langlois writes: > Mark H Weaver writes: > >> One possible solution might be to update the replacement (graft) for >> _curl_ so that it's *built* against nghttp2-1.41. Something like this >> (untested): > > I'm afraid this still doesn't solve the problem. AFAIU, grafting the new > curl happens after building r-v8, so at link time it still sees the old > nghttp2 version. Ah yes, that makes sense. > Instead, I'm thinking your suggestion of leaving 'node' at 10.19 for now > (or 10.20, I can try that) and then introduce a 'node-10.22' package > that can be used for Icecat is better. That indeed might be the best approach for now. > I can do that. How does that sound? Sure, sounds good. Thanks! Mark