From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to version 23.1.9.
Date: Thu, 12 Oct 2023 04:13:17 +0200 [thread overview]
Message-ID: <20231012021317.ZuRE9TYNr0XEQfaRz-fUGY3fIiIkepraBXHRPGh4AoY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46172@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/46172#issuecomment-1758806108
Comment:
It's better to fix the cross-cc wrappers instead of hacking into the template
```diff
commit 288dedd830a (HEAD -> master)
Author: Đoàn Trần Công Danh <congdanhqx@gmail.com>
Date: Thu Oct 12 09:09:38 2023 +0700
wrappers/cross-cc: drop -isystem /usr/include, too
diff --git a/common/wrappers/cross-cc b/common/wrappers/cross-cc
index 0e08bc91d0f..9f9d581a8b7 100644
--- a/common/wrappers/cross-cc
+++ b/common/wrappers/cross-cc
@@ -23,13 +23,13 @@ while [ $i -lt ${#ARGS[@]} ]; do
MYARGS+=("-L${arg}")
fi
unset libpath
- elif [ "$arg" = "-I" ]; then
+ elif [ "$arg" = "-I" -o "$arg" = "-isystem" ]; then
incpath=1
elif [ "$arg" = "-L" ]; then
libpath=1
- elif [ "$arg" = "-I/usr/include" -o "$arg" = "-L/usr/lib" \
+ elif [ "$arg" = "-I/usr/include" -o "$arg" = "-isystem/usr/include" \
-o "$arg" = "-L/usr/lib32" -o "$arg" = "-L/usr/lib64" \
- -o "$arg" = "-L/lib" ]; then
+ -o "$arg" = "-L/usr/lib" -o "$arg" = "-L/lib" ]; then
echo "[cc-wrapper] ignoring $arg"
else
MYARGS+=("${arg}")
```
next prev parent reply other threads:[~2023-10-12 2:13 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 20:02 [PR PATCH] mesa: update to version 23.1.8 SpidFightFR
2023-09-21 20:03 ` [PR PATCH] [Updated] " SpidFightFR
2023-09-21 20:05 ` SpidFightFR
2023-09-21 20:14 ` SpidFightFR
2023-09-21 20:29 ` mhmdanas
2023-09-21 20:29 ` mhmdanas
2023-09-22 4:03 ` SpidFightFR
2023-09-26 13:02 ` SpidFightFR
2023-09-26 13:03 ` SpidFightFR
2023-09-30 12:14 ` [PR PATCH] [Updated] " SpidFightFR
2023-09-30 12:15 ` mesa: update to version 23.2.1 SpidFightFR
2023-09-30 12:36 ` SpidFightFR
2023-10-02 9:45 ` SpidFightFR
2023-10-07 7:21 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-07 7:44 ` SpidFightFR
2023-10-07 13:46 ` mesa: update to version 23.1.9 mhmdanas
2023-10-07 13:47 ` mhmdanas
2023-10-07 13:58 ` SpidFightFR
2023-10-07 13:58 ` SpidFightFR
2023-10-10 7:10 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-10 7:28 ` SpidFightFR
2023-10-10 7:28 ` SpidFightFR
2023-10-10 7:28 ` SpidFightFR
2023-10-10 7:33 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-10 7:40 ` SpidFightFR
2023-10-11 17:15 ` SpidFightFR
2023-10-11 17:36 ` Johnnynator
2023-10-11 17:46 ` Johnnynator
2023-10-11 17:57 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-11 17:58 ` SpidFightFR
2023-10-11 17:59 ` SpidFightFR
2023-10-11 18:01 ` SpidFightFR
2023-10-11 18:02 ` SpidFightFR
2023-10-12 2:13 ` sgn [this message]
2023-10-12 12:45 ` sgn
2023-10-12 19:07 ` SpidFightFR
2023-10-14 7:29 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 17:30 ` SpidFightFR
2023-10-16 17:34 ` SpidFightFR
2023-10-16 17:35 ` mesa: update to version 23.2.1 SpidFightFR
2023-10-16 17:38 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 17:48 ` Anachron
2023-10-16 18:01 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 18:03 ` SpidFightFR
2023-10-16 18:20 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 18:20 ` SpidFightFR
2023-11-01 3:39 ` rationalize-zz
2023-11-01 10:20 ` [PR PATCH] [Updated] " SpidFightFR
2023-11-01 10:20 ` SpidFightFR
2023-11-01 10:42 ` SpidFightFR
2023-11-01 16:13 ` [PR REVIEW] " Johnnynator
2023-11-01 16:22 ` SpidFightFR
2023-11-01 16:26 ` [PR PATCH] [Updated] " SpidFightFR
2023-11-01 17:09 ` [PR REVIEW] " SpidFightFR
2023-11-02 9:12 ` [PR PATCH] [Merged]: " Johnnynator
2023-11-02 9:13 ` Johnnynator
2023-11-02 17:37 ` SpidFightFR
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=20231012021317.ZuRE9TYNr0XEQfaRz-fUGY3fIiIkepraBXHRPGh4AoY@z \
--to=sgn@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).