From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id IDuJAr7TAGZJVAAA62LTzQ:P1 (envelope-from ) for ; Mon, 25 Mar 2024 02:30:38 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id IDuJAr7TAGZJVAAA62LTzQ (envelope-from ) for ; Mon, 25 Mar 2024 02:30:38 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=protonmail.com header.s=protonmail3 header.b=m4XlP7IY; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gnu.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1711330237; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:resent-cc: resent-from:resent-sender:resent-message-id:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=KlOFiGhHmRe3uRmD+y1xEgCf2GABz6ncYGWtSQYxEJc=; b=QLqvQDn1Agf2ntGMX110k4dq1jTJBpQgo2uRbDYS6twuxALbwrIQ5i0ljXqIKSDjxeGOZU ElZxJtjlQjlCTrhqXSrBKnPfOHUvzflnpazKjuw+yeHd82j+ZbfDjCJfPvrIsRLQfNB2aE RaF9SWD6CN+Yy/bYLrcIpZfrKb/PE79ZSzTVdZWmFFPwwN334y+qG/3J/gUqrnkwWDvhSk 2BJwnT4FcIqtHfmzyAaIxaSyFuzqHQ7GV96RIoeEyU4E6KHiHMREZhB31/FcB5ONakoSR7 IX7ny6cff6fngQ1o5rbum+RWn78G5tMubUgkRgymwd/UiznW1rFgAsHewh+znQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=protonmail.com header.s=protonmail3 header.b=m4XlP7IY; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gnu.org ARC-Seal: i=1; s=key1; d=yhetil.org; t=1711330237; a=rsa-sha256; cv=none; b=jpwGBSWlKEUw8zka+lZpEQCFJXYjyOax+kasrruLtLyiqycHQzpAnZXzQF/v/m/nPeSgd1 e1B/nCu/cKcSyVrKQo+7IO5pPz90a8AbMYqaJbN6r1YclcLIzS6TlCo0/QXn9VXixpu4Zg IkBpylOTR0TCjlM4d+Ef6+NJTEzsEhxgyqIwWEEt5fJ8PQmAsr3VtcCh8KFG/duMi4IOyo cv+UtWC81IJufg8JAwgEs3P0lvIBdPU8BMczFgYnDSDjx7RNKF6HKIskus58WKFu1RrXLC PwpgH4x5GGtvPH5+Har13XGyfhmbMAhpeOBKHXAaH3rqxL3nJV+R6DoAy+IIVw== 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 D756C6F83E for ; Mon, 25 Mar 2024 02:30:36 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1roZAM-0003pW-96; Sun, 24 Mar 2024 21:30:22 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1roZAK-0003pN-Ex for guix-patches@gnu.org; Sun, 24 Mar 2024 21:30:20 -0400 Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1roZAK-0003E9-6u for guix-patches@gnu.org; Sun, 24 Mar 2024 21:30:20 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1roZB0-0005Wd-7W for guix-patches@gnu.org; Sun, 24 Mar 2024 21:31:02 -0400 X-Loop: help-debbugs@gnu.org Subject: [bug#69637] [PATCH mesa-updates v2 0/5] gnu: mesa: Update to 24.0.3. Resent-From: John Kehayias Original-Sender: "Debbugs-submit" Resent-CC: guix-patches@gnu.org Resent-Date: Mon, 25 Mar 2024 01:31:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 69637 X-GNU-PR-Package: guix-patches X-GNU-PR-Keywords: patch To: aurtzy Cc: 69637@debbugs.gnu.org, efraim@flashner.co.il Received: via spool by 69637-submit@debbugs.gnu.org id=B69637.171133025021210 (code B ref 69637); Mon, 25 Mar 2024 01:31:02 +0000 Received: (at 69637) by debbugs.gnu.org; 25 Mar 2024 01:30:50 +0000 Received: from localhost ([127.0.0.1]:47662 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1roZAn-0005W2-DL for submit@debbugs.gnu.org; Sun, 24 Mar 2024 21:30:49 -0400 Received: from mail-4316.protonmail.ch ([185.70.43.16]:26659) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1roZAk-0005Vg-RZ for 69637@debbugs.gnu.org; Sun, 24 Mar 2024 21:30:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1711330196; x=1711589396; bh=KlOFiGhHmRe3uRmD+y1xEgCf2GABz6ncYGWtSQYxEJc=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=m4XlP7IYi8YlM6KktYxcKwdvYPbdqrA+13yWjP78jz1MlnCoJCZUs6BrmVGCsQaCe WPPE3xt5lcDFIFWE0EdwHPxSyyJFmzZRvyClGI6GmGdgKatlCPSYiVrgR3KiCu8Ici b+2s3jF/eKKax2MDBRiWLuUZrXqvOtzYoF/2ndP7DvQfZYMpSmUO/pJt7toMKkmign CM3MeeZ+JPkN4JSXc+uhienS9ZTxY0cxJokOSm9IBCpfiDe2rvUPbWTklLVBJ54zf2 cXXLAXsDjD6DpzFMzErrGQUALg9w4d2+tb2BXg0CdO4PpJ6ai6z0zJdXu1EId3GJyC i6NUNa4TJ7W1g== Date: Mon, 25 Mar 2024 01:29:42 +0000 Message-ID: <87sf0fnloc.fsf@protonmail.com> In-Reply-To: References: Feedback-ID: 7805494:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: guix-patches@gnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-to: John Kehayias X-ACL-Warn: , John Kehayias via Guix-patches From: John Kehayias via Guix-patches via Errors-To: guix-patches-bounces+larch=yhetil.org@gnu.org Sender: guix-patches-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Queue-Id: D756C6F83E X-Spam-Score: -6.83 X-Migadu-Spam-Score: -6.83 X-Migadu-Scanner: mx10.migadu.com X-TUID: twSDaku30D2T Hi aurtzy and Efraim, On Fri, Mar 22, 2024 at 03:24 AM, aurtzy wrote: > New patchset coming in. Mesa has been updated to 24.0.3, and I've added = TODO > comments for future work as suggested. > Thanks! >> I would like to get the build farm cranking on the updates I have >> queued for mesa-updates (cairo, libdrm, mesa, vulkan). We could also >> do just the version update of mesa to start, or just NVK on x86_64, >> leaving future changes for the next round. I don't have a preference >> myself, other than wanting to get this branch moving with these >> updates. > > NVK on 24.0.3 is also still considered experimental, so if that's a conce= rn we > could save this work for 24.1 when it's planned to move out of this stage= . > Right, I forgot about that. I also remember that it depends (or is helped by) some changes in recent kernels, 6.7 and/or 6.8 if I remember. So, maybe we can take this approach: 1. Make the update just to 24.0.3 for mesa (does that require newer meson?) 2. Add any rust packages as needed to master 3. Either add a mesa-next (to master?) or followup on mesa-updates after it gets merged to master with a mesa based on 24.1 (as soon as it is tagged) with NVK enabled. This will let us at least get mesa built and make for a headstart come 24.0.1. With 24.1 soon ("this quarter"?) and how long it can take us to build on non-x86 architectures, it would be nice to have that go quickly. Since I'll be including cairo, libdrm, and vulkan updates (at least) this round, I anticipate it taking a bit. Does that sound okay? It'll give some time to test things and clean up/find alternatives as Efraim suggested. I'm also not opposed to just enabling NVK now. In that case, we should have one commit to just update mesa and another to enable NVK. >> I also tried a couple of different options. The one that I most want >> involved using with-output-to-file to rewrite the wrap file and >> replacing all the fields. I borrowed the file-sha256 function from >> guix/build/cargo-utils.scm to get the source_hash. In the end I wasn't >> able to get the gexp and un-gexp bits working to actually get the file >> written. >> >> When I kept a failed build I saw that the 'directory' field is the >> directory into which meson writes the meson.build file, which is why >> using a different version of the rust crate caused problems with >> src/lib.rs not existing. I suppose we could start from your patch and >> then, after running substitute, extract the tarball into either a >> hardcoded path (determined after manually reading the sources) or we can >> extract the 'directory' field by reading the sources and then untar the >> source there. > > Noted, thanks Efraim! I'll keep looking into this. > Thanks both of you! I would like to start pushing patches and building everything in the next few days, especially as some have sat for a while and it will take time to build. John