From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id QMESN2eT+2VsoQAA62LTzQ:P1 (envelope-from ) for ; Thu, 21 Mar 2024 02:54:48 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id QMESN2eT+2VsoQAA62LTzQ (envelope-from ) for ; Thu, 21 Mar 2024 02:54:48 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20230601 header.b=MHvXPJX5; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); 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" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1710986087; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: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=2Z/BxiYNJaun481ANI9ahpr17J7Vcq4OY5Q3dIwutd8=; b=KETTTM5oTFAeBD5+fd+CmfkWkkXUHoxUG+m0TxApkgDxS492b1oiTZrPXdCL77dZQDtdKp 9ngsxfW3GECLjIY8PNkQ1EVGWb4Z77kWE9DBGbdl7dRbBhOBvUMSObQ8A2HLlkhUwD6Vkz 1CbRTNc5NwZm9jN0yFu8b7qV8bcFm6yfuRkjUxwB6z9wNhtd9fVEz1E8ORs6LdVWc1kck/ PRsp1GB9sZ3DVj/V1ZMwic+AUU785dFM88BG3htaJjQ55SSEaTQRgp5oTZlNTfo86auC7R 7G11hUxGRYu8cXL93h89CPH3AeOViZvJn/I1qpvwQUe0lD1fRFVxeUxcWlopQA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20230601 header.b=MHvXPJX5; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); 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" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1710986087; a=rsa-sha256; cv=none; b=XPzKIuJHFcPNwbvkGK7dyNHafeuNx+S4jcz+JEH3FY0+RKJLrcyRxZZ//4qd36Xn6u8z5U m+E5UzLgAFH7aBUoMMIYg3VBjLKU+IxfeXyZQVoKSGqqyXylsl9Xijd2ceqppAhSB1uvAA ILOLzFj7GpkLKkiyovfEOG2HhCu91q4QdYdbKbmi/aIXTdm6pREBRvxxCQAnjcbwJVjhQv hEJBrnHRvZO77txy84Wp/r5WxzFLo0GlsPJZ7CmoWnZop9FFxqOHbwQoIc1Jubx6FVSgc8 jm5ZE7apVzl3Tgk2UrxglpvUrlQ4FF/tL1giclwBNsAvms2fuE3iOkibeAgIqQ== 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 4FD5E38B53 for ; Thu, 21 Mar 2024 02:54:46 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rn7dP-0004F2-RS; Wed, 20 Mar 2024 21:54:23 -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 1rn7dO-0004Ec-Es for guix-patches@gnu.org; Wed, 20 Mar 2024 21:54:22 -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 1rn7dO-0005e6-6m for guix-patches@gnu.org; Wed, 20 Mar 2024 21:54:22 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rn7e1-0002gm-RK for guix-patches@gnu.org; Wed, 20 Mar 2024 21:55:01 -0400 X-Loop: help-debbugs@gnu.org Subject: [bug#69637] [PATCH mesa-updates 0/6] gnu: mesa: Update to 24.0.2. Resent-From: aurtzy Original-Sender: "Debbugs-submit" Resent-CC: guix-patches@gnu.org Resent-Date: Thu, 21 Mar 2024 01:55:01 +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: Efraim Flashner Cc: john.kehayias@protonmail.com, 69637@debbugs.gnu.org Received: via spool by 69637-submit@debbugs.gnu.org id=B69637.171098606610228 (code B ref 69637); Thu, 21 Mar 2024 01:55:01 +0000 Received: (at 69637) by debbugs.gnu.org; 21 Mar 2024 01:54:26 +0000 Received: from localhost ([127.0.0.1]:44750 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rn7dR-0002et-Ne for submit@debbugs.gnu.org; Wed, 20 Mar 2024 21:54:26 -0400 Received: from mail-qt1-f169.google.com ([209.85.160.169]:55428) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rn7dP-0002eW-C2 for 69637@debbugs.gnu.org; Wed, 20 Mar 2024 21:54:24 -0400 Received: by mail-qt1-f169.google.com with SMTP id d75a77b69052e-430b6ff2a20so3025801cf.2 for <69637@debbugs.gnu.org>; Wed, 20 Mar 2024 18:53:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710985958; x=1711590758; darn=debbugs.gnu.org; h=in-reply-to:content-language:references:cc:to:subject:from :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=2Z/BxiYNJaun481ANI9ahpr17J7Vcq4OY5Q3dIwutd8=; b=MHvXPJX52A1rYWcr7vcNpKtcu1BOHImWRpirnJ6UOagyFSoixEGHUj7agijFMTRsJ2 wp4etvF8dolMO0ev1Yi93ZDygv5FLoEM56dVc6wFST42VzCO+dPgNoGLRn3YmcQsoMjL UZPqYj6Am8bnQqw6l2iMhzXh7K3Wr/rk4OBt2DGDsqEnSQ3gSpJlfgruGnotyLuOe9fR RnPUaYJs2if7LeOcCP9idZokll/sacnPw4hxqUlLVFjne1B+xy21KK3QsYjvA0UzLTI3 2iCB61nLhzMZ3nmk91SuQaVxNAFBoAbDgPAHaBG6Gq6sQfMbIMuq3YhakKDgd66sgAN/ nRjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710985958; x=1711590758; h=in-reply-to:content-language:references:cc:to:subject:from :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=2Z/BxiYNJaun481ANI9ahpr17J7Vcq4OY5Q3dIwutd8=; b=DHuZVii9kQdoOiCrVEh/8B6+zNnEyL3JOjfRjE+vz8ZtwwFRi4D8uEi5JZVjq0/Q31 uQHeQe5NlqbL6f3u+/R4YkJcPauFSb1xVrVDfV7aXIPLfwsEqtQd6ubr6g4XYhloSMBZ vcMOtqlgpr2QZQoLvM0aXe3DEapCs/m++Ddl0wjNneA2AstJIv/8qyclWaOGtF89itpM lWV5K5+G7dIfvYSv68G2Rhyyc/O+z7sNqLHo5eKH+BDrSvRQM9ksMDaEq339ng3/ajql DgEj81MzTskP+pZNK/26RJbSgDykdAu7arB550NEZGQcGT6PnUUOlAx/ZLpiuj086duX q9bg== X-Gm-Message-State: AOJu0YxX29q9xoyTYfs2HlNkcN9wtMdRxKQl0qYIT1341aIvLaOVJXb5 ftTnRpS189P4ZaogcEGq5mTW+EG23nF8lFBowh0m4QeXrxwKYokw X-Google-Smtp-Source: AGHT+IFCSTI1by0t3VcRm6+YtGSM5VFyqKoR6rYLNR4ygZVYj+90ujLzUj1gqscMtcshUafaxDA7mw== X-Received: by 2002:ac8:5dd1:0:b0:430:ec9c:44bd with SMTP id e17-20020ac85dd1000000b00430ec9c44bdmr4404954qtx.60.1710985957817; Wed, 20 Mar 2024 18:52:37 -0700 (PDT) Received: from [192.168.1.87] (ool-18bb63f6.dyn.optonline.net. [24.187.99.246]) by smtp.gmail.com with ESMTPSA id hg1-20020a05622a610100b00430b5dcac34sm6506945qtb.8.2024.03.20.18.52.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Mar 2024 18:52:37 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------KqdKmMzObqQmrgNhcYVvh4kN" Message-ID: Date: Wed, 20 Mar 2024 21:52:36 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: aurtzy References: Content-Language: en-US In-Reply-To: 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: , 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-Spam-Score: -5.21 X-Spam-Score: -5.21 X-Migadu-Queue-Id: 4FD5E38B53 X-Migadu-Scanner: mx11.migadu.com X-TUID: rCFwsMVBAXHT This is a multi-part message in MIME format. --------------KqdKmMzObqQmrgNhcYVvh4kN Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 3/12/24 04:11, Efraim Flashner wrote: > Are there other architectures which have rust based drivers? x86_64 > isn't the only architecture which has rust building on it. There doesn't appear to be any official documentation stating architecture requirements for Mesa with NVK/Rust, however I have added few new inputs other than rust to get NVK working. I've only done extensive testing with x86_64 so I was unsure of potential issues with including this on other architectures (other than i686 not building rust). > The crates are also available in > %output/share/cargo/registry/name-version.crate, although I can't think > of a good way to address them by name without using find-files. > > I would personally replace the versions requested by mesa with whatever > version we happen to have in guix so that we don't have to add special > versions just for mesa. I have/had tried a few approaches to use the crates already available in Guix with no success so far. I've outlined the approaches below; still looking into solutions, but perhaps there's something I'm missing or haven't tried yet? - Simply including crates as (native-)inputs does not make them discoverable by meson. - Mesa uses these *.wrap files which specify the rust dependency versions, source URLs, and tar hashes. I currently get the build working by relying on meson to fall back to "downloading" from a patched source URL (pointing to store), although it still has to match the hash. - I recently discovered a way to disable the hash requirement so I could use a different input version (i.e. one from Guix), but doing it causes "File src/lib.rs does not exist" errors. I'm still looking into this right now, as it seems promising. - Old IRC logs point to projects like newsboat and librsvg which also mix cargo with with another build system, but these start with cargo-build-system with phases added/replaced from the second build system. Cargo.toml doesn't exist in Mesa either (which cargo-build-system seems to depend on), so experimenting with using cargo-build-system didn't yield much. I wanted to look more into the third bullet before responding, but I felt it would be unfortunate to have this information rot while trying to make time for hacking - hopefully it's still useful. Cheers, aurtzy --------------KqdKmMzObqQmrgNhcYVvh4kN Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
On 3/12/24 04:11, Efraim Flashner wrote:
Are there other architectures which have rust based drivers? x86_64
isn't the only architecture which has rust building on it.
There doesn't appear to be any official documentation stating architecture requirements for Mesa with NVK/Rust, however I have added few new inputs other than rust to get NVK working. I've only done extensive testing with x86_64 so I was unsure of potential issues with including this on other architectures (other than i686 not building rust).
The crates are also available in
%output/share/cargo/registry/name-version.crate, although I can't think
of a good way to address them by name without using find-files.

I would personally replace the versions requested by mesa with whatever
version we happen to have in guix so that we don't have to add special
versions just for mesa.

I have/had tried a few approaches to use the crates already available in Guix with no success so far. I've outlined the approaches below; still looking into solutions, but perhaps there's something I'm missing or haven't tried yet?

- Simply including crates as (native-)inputs does not make them discoverable by meson.

- Mesa uses these *.wrap files which specify the rust dependency versions, source URLs, and tar hashes. I currently get the build working by relying on meson to fall back to "downloading" from a patched source URL (pointing to store), although it still has to match the hash.

- I recently discovered a way to disable the hash requirement so I could use a different input version (i.e. one from Guix), but doing it causes "File src/lib.rs does not exist" errors. I'm still looking into this right now, as it seems promising.

- Old IRC logs point to projects like newsboat and librsvg which also mix cargo with with another build system, but these start with cargo-build-system with phases added/replaced from the second build system. Cargo.toml doesn't exist in Mesa either (which cargo-build-system seems to depend on), so experimenting with using cargo-build-system didn't yield much.

I wanted to look more into the third bullet before responding, but I felt it would be unfortunate to have this information rot while trying to make time for hacking - hopefully it's still useful.

Cheers,

aurtzy

--------------KqdKmMzObqQmrgNhcYVvh4kN--