From: KF-Art <KF-Art@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: gamescope
Date: Fri, 10 Mar 2023 05:42:37 +0100 [thread overview]
Message-ID: <20230310044237.itBdZwEyshjQMHrLsZWyZ9fpklfJYAu91QYniqTN9Vw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36869@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
New comment by KF-Art on void-packages repository
https://github.com/void-linux/void-packages/issues/36869#issuecomment-1463251830
Comment:
> I tried, but I gave up.
>
> [diff.txt](https://github.com/void-linux/void-packages/files/9003858/diff.txt)
>
> Fails on this error ¯\_(ツ)_/¯
>
> ```
>
>
> ../subprojects/libliftoff/test/libdrm_mock.c:117:6: error: variable 'ret' set but not used [-Werror=unused-but-set-variable]
> 117 | int ret;
> | ^~~
> cc1: all warnings being treated as errors
> ```
Using ` -Wno-unused-but-set-variable` to `libliftoff` `meson.build` seems to correct it. I made a patch for that.
```
diff -ruN a/meson.build b/meson.build
--- a/meson.build 2023-03-05 12:36:15.000000000 -0600
+++ b/meson.build 2023-03-09 21:04:10.598647298 -0600
@@ -23,6 +23,7 @@
'-Wno-missing-braces',
'-Wno-unused-parameter',
+ '-Wno-unused-but-set-variable',
]), language: 'c')
liftoff_inc = include_directories('include')
```
next prev parent reply other threads:[~2023-03-10 4:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 5:25 [ISSUE] " 0-st
2022-06-28 18:44 ` TeddyDD
2022-07-09 19:23 ` classabbyamp
2022-07-09 19:23 ` classabbyamp
2022-07-13 5:44 ` birb7
2022-10-04 6:05 ` classabbyamp
2022-11-02 20:43 ` TeddyDD
2023-03-10 4:42 ` KF-Art [this message]
2023-05-15 2:02 ` HadetTheUndying
2023-05-15 7:08 ` TeddyDD
2024-02-12 1:31 ` jaminW55
2024-02-27 18:35 ` mdkcore0
2024-02-27 18:38 ` [ISSUE] [CLOSED] " classabbyamp
2024-01-31 0:12 [ISSUE] " jaminW55
2024-01-31 0:15 ` jaminW55
2024-01-31 0:15 ` jaminW55
2024-01-31 0:16 ` jaminW55
2024-01-31 2:27 ` chrysos349
2024-01-31 3:09 ` jaminW55
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=20230310044237.itBdZwEyshjQMHrLsZWyZ9fpklfJYAu91QYniqTN9Vw@z \
--to=kf-art@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).