From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Vulkan 1.3.211.0
Date: Sun, 15 May 2022 18:49:22 +0200 [thread overview]
Message-ID: <20220515164922.b2qngQQstKl1554raxhD9m39q_sVa47xJl3XuSzDfaQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37082@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
New comment by tibequadorian on void-packages repository
https://github.com/void-linux/void-packages/pull/37082#issuecomment-1126976844
Comment:
Related: https://github.com/KhronosGroup/Vulkan-Loader/issues/881
I explicitly disabled GAS for cross builds now like done in https://github.com/gador/nixpkgs/commit/8e1009a9b869375b4b4c4429fb76024f0241ce46
It looks like in older versions, cross compiling didn't fail because the build logic was wrong.
This got fixed in https://github.com/KhronosGroup/Vulkan-Loader/commit/db5e3d0f454f063db7b4505e4d08b759f1874bbb which makes it fail now.
Because it never really used GAS there should be nothing wrong with disabling it explicitly now.
What do you think @ericonr?
next prev parent reply other threads:[~2022-05-15 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 19:27 [PR PATCH] " tibequadorian
2022-05-11 19:31 ` tibequadorian
2022-05-11 19:40 ` tibequadorian
2022-05-14 0:37 ` ericonr
2022-05-14 1:40 ` tibequadorian
2022-05-14 1:41 ` tibequadorian
2022-05-15 16:34 ` [PR PATCH] [Updated] " tibequadorian
2022-05-15 16:46 ` tibequadorian
2022-05-15 16:49 ` tibequadorian [this message]
2022-06-07 19:46 ` tibequadorian
2022-06-12 11:29 ` tibequadorian
2022-06-14 13:33 ` tibequadorian
2022-09-13 2:14 ` github-actions
2022-09-15 0:15 ` Seltyk
2022-09-16 17:34 ` tibequadorian
2022-09-16 17:34 ` [PR PATCH] [Closed]: " tibequadorian
2022-11-25 0:18 ` tibequadorian
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=20220515164922.b2qngQQstKl1554raxhD9m39q_sVa47xJl3XuSzDfaQ@z \
--to=tibequadorian@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).