From: HanoJing <HanoJing@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Reason for deletion of srcpkgs/mesa/patches/0001-radeonsi-On-Aarch64-force-persistent-buffers-to-GTT.patch ?
Date: Thu, 16 Jun 2022 18:49:42 +0200 [thread overview]
Message-ID: <20220616164942.4icOgHzZWTMbAwxKjtoRqGY67050JvJe-BsoXaVpw1U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37579@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]
New comment by HanoJing on void-packages repository
https://github.com/void-linux/void-packages/issues/37579#issuecomment-1157908459
Comment:
> > Also, the files in my local repository have _1 not _2 like so: mesa-22.1.1_1.aarch64.xbps
>
> Did you build based off the PR then?
>
> Even if you didn't, you should see it applying the patches.
>
> ```
> => mesa-22.1.1_2: running do_patch ...
> => mesa-22.1.1_2: running do-patch hook: 00-patches ...
> => mesa-22.1.1_2: patching: 0001-radeonsi-On-Aarch64-force-persistent-buffers-to-GTT.patch.
> => mesa-22.1.1_2: patching: add-use-elf-tls.patch.
> => mesa-22.1.1_2: patching: megadriver-symlinks.patch.
> => mesa-22.1.1_2: patching: musl-endian.patch.
> => mesa-22.1.1_2: patching: musl-stacksize.patch.
> => mesa-22.1.1_2: patching: musl.patch.
> ```
>
> > Thanks for the quick reply! I tried the xi -u mesa method but It sttill pulls the mesa out the normal void repos.
>
> Are you sure? Run it with `-v`.
>
> ```
> Found MesaLib-devel-22.1.1_2 in repository /home/andrewb/Projects/void-packages/hostdir/binpkgs/fix_37579
> Found mesa-dri-22.1.1_2 in repository /home/andrewb/Projects/void-packages/hostdir/binpkgs/fix_37579
> Found mesa-22.1.1_2 in repository /home/andrewb/Projects/void-packages/hostdir/binpkgs/fix_37579
> Found libglapi-22.1.1_2 in repository /home/andrewb/Projects/void-packages/hostdir/binpkgs/fix_37579
> Found libOSMesa-22.1.1_2 in repository /home/andrewb/Projects/void-packages/hostdir/binpkgs/fix_37579
> Found libgbm-22.1.1_2 in repository /home/andrewb/Projects/void-packages/hostdir/binpkgs/fix_37579
> Found libgbm-devel-22.1.1_2 in repository /home/andrewb/Projects/void-packages/hostdir/binpkgs/fix_37579
> Found libxatracker-22.1.1_2 in repository /home/andrewb/Projects/void-packages/hostdir/binpkgs/fix_37579
> Found mesa-opencl-22.1.1_2 in repository /home/andrewb/Projects/void-packages/hostdir/binpkgs/fix_37579
> ```
Yes, thanks for the hint! I ran `xi -uv mesa` and it found the binpkg: `Found mesa-22.1.1_1 in repository /home/user/Projekte/void-packages/hostdir/binpkgs`
I also see that the patch is getting applied:
`=> mesa-22.1.1_1: patching: 0001-radeonsi-On-Aarch64-force-persistent-buffers-to-GTT.patch.`
This patch is only getting applied on the mesa library itself, not on any of it's subpackages (like mesa-dri for example), right?
I'd have to rip my system apart in order to install the built mesa subpackages.
next prev parent reply other threads:[~2022-06-16 16:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 21:22 [ISSUE] " HanoJing
2022-06-16 1:33 ` abenson
2022-06-16 7:44 ` HanoJing
2022-06-16 7:58 ` paper42
2022-06-16 11:01 ` HanoJing
2022-06-16 11:26 ` HanoJing
2022-06-16 11:36 ` HanoJing
2022-06-16 11:36 ` HanoJing
2022-06-16 12:06 ` HanoJing
2022-06-16 12:24 ` HanoJing
2022-06-16 12:27 ` HanoJing
2022-06-16 12:56 ` HanoJing
2022-06-16 12:57 ` HanoJing
2022-06-16 14:00 ` abenson
2022-06-16 14:02 ` abenson
2022-06-16 14:04 ` abenson
2022-06-16 16:49 ` HanoJing [this message]
2022-06-16 16:51 ` HanoJing
2022-06-16 16:57 ` abenson
2022-06-16 17:18 ` HanoJing
2022-06-16 18:35 ` HanoJing
2022-06-16 18:35 ` [ISSUE] [CLOSED] " HanoJing
2022-06-16 19:17 ` HanoJing
2022-06-16 19:18 ` HanoJing
2022-06-16 19:32 ` HanoJing
2022-06-16 19:34 ` HanoJing
2022-06-16 19:35 ` HanoJing
2022-06-16 19:45 ` abenson
2022-06-16 20:12 ` HanoJing
2022-06-16 21:27 ` HanoJing
2022-06-16 21:29 ` HanoJing
2022-06-16 21:34 ` HanoJing
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220616164942.4icOgHzZWTMbAwxKjtoRqGY67050JvJe-BsoXaVpw1U@z \
--to=hanojing@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).