From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to version 24.0.1.
Date: Fri, 16 Feb 2024 17:34:56 +0100 [thread overview]
Message-ID: <20240216163456.199AD23D1E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48480@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
New comment by zlice on void-packages repository
https://github.com/void-linux/void-packages/pull/48480#issuecomment-1948832094
Comment:
ok so this works for x86, a64, a7l
```sh
post_configure() {
if [ "$CROSS_BUILD" ]; then
find -iname "*.ninja" -exec sed -i "{}" \
-e "/rustc/s; --sysroot ${XBPS_CROSS_BASE}/usr;;g" \
-e "s|-isystem/usr/include||g" \
\;
fi
}
```
it looks like ninja build has `-isystem/usr/include` for everything, so aarch64 gets x86_64's gnu stub.h ... which wants -32, which a64 doesn't have.
<details>
<summary>screenshot ninja build llvm_bindings</summary>
</details>
next prev parent reply other threads:[~2024-02-16 16:34 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 18:11 [PR PATCH] mesa: update to version 24.0.0 SpidFightFR
2024-02-01 18:15 ` SpidFightFR
2024-02-02 6:42 ` classabbyamp
2024-02-02 8:02 ` SpidFightFR
2024-02-03 17:24 ` SpidFightFR
2024-02-09 12:13 ` [PR PATCH] [Updated] " SpidFightFR
2024-02-09 12:15 ` SpidFightFR
2024-02-15 2:37 ` zlice
2024-02-15 12:32 ` SpidFightFR
2024-02-15 12:35 ` zlice
2024-02-15 12:36 ` SpidFightFR
2024-02-15 12:46 ` [PR PATCH] [Updated] " SpidFightFR
2024-02-15 12:47 ` SpidFightFR
2024-02-15 21:11 ` dkwo
2024-02-15 23:55 ` SpidFightFR
2024-02-16 10:15 ` [PR PATCH] [Updated] " SpidFightFR
2024-02-16 10:15 ` SpidFightFR
2024-02-16 12:22 ` [PR PATCH] [Updated] " SpidFightFR
2024-02-16 12:25 ` SpidFightFR
2024-02-16 12:26 ` mesa: update to version 24.0.1 SpidFightFR
2024-02-16 12:27 ` [PR PATCH] [Updated] " SpidFightFR
2024-02-16 13:41 ` zlice
2024-02-16 13:41 ` zlice
2024-02-16 13:42 ` zlice
2024-02-16 13:50 ` dkwo
2024-02-16 13:54 ` zlice
2024-02-16 13:55 ` [PR PATCH] [Updated] " SpidFightFR
2024-02-16 13:56 ` SpidFightFR
2024-02-16 13:57 ` zlice
2024-02-16 16:34 ` zlice
2024-02-16 16:34 ` zlice [this message]
2024-02-16 16:57 ` SpidFightFR
2024-02-16 17:00 ` zlice
2024-02-16 17:02 ` SpidFightFR
2024-02-16 17:39 ` dkwo
2024-02-16 17:45 ` zlice
2024-02-16 18:17 ` [PR PATCH] [Updated] " SpidFightFR
2024-02-16 18:22 ` SpidFightFR
2024-02-16 18:43 ` SpidFightFR
2024-02-16 19:39 ` dkwo
2024-02-16 22:44 ` SpidFightFR
2024-02-28 19:51 ` [PR PATCH] [Updated] " SpidFightFR
2024-02-28 20:02 ` SpidFightFR
2024-02-28 20:20 ` zlice
2024-02-28 20:24 ` mesa: update to version 24.0.2 SpidFightFR
2024-02-28 20:25 ` SpidFightFR
2024-03-04 19:44 ` SpidFightFR
2024-03-09 9:06 ` Daxot
2024-03-09 10:50 ` SpidFightFR
2024-03-09 15:03 ` [PR PATCH] [Updated] " SpidFightFR
2024-03-09 15:05 ` SpidFightFR
2024-03-10 13:08 ` [PR PATCH] [Merged]: " Johnnynator
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=20240216163456.199AD23D1E@inbox.vuxu.org \
--to=zlice@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).